search

uberVU / elasticboard

Dashboard that aggregates relevant metrics for Open Source projects.
http://elasticboard.mihneadb.net/landing.html
MIT License
61 stars 7 forks source link

Broken/incompatible/out of date branches #46

Closed ovidiuch closed 10 years ago

ovidiuch commented 10 years ago

We should be notified of branches that are no longer compatible with their upstream branch (master or project branch) whenever conflicts appear.

Just as the merge button works, but together on a board, maybe with alerts :)

I for one want to find out asap when my branch is no longer compatible with the one I want to merge it back into, to not waste my time branching out even further.

mihneadb commented 10 years ago

I'm thinking for every event that we get that a branch was updated we would have to try and merge it and see if the changes apply OK. If they do, keep a green light, if not, alert. This approach requires adding some extra state/information to the data store, but it's better than performing the check on every page load.

ovidiuch commented 10 years ago

Yes, of course, this is got GitHub does it already

mihneadb commented 10 years ago

Github API only gives data about if a branch is mergeable for pull requests (see here). I know we use a pull request for every issue, so would it be a good start to have a widget showing which pull requests are not mergeable?

cc @skidding

ovidiuch commented 10 years ago

Yes, of course, this is got GitHub does it already

I don't know what was I typing there...

Github API only gives data about if a branch is mergeable for pull requests (see here). I know we use a pull request for every issue, so would it be a good start to have a widget showing which pull requests are not mergeable?

Yup, pull requests are the biggest use case.

mihneadb commented 10 years ago

Added. Fortunately, there's no such PR for thehole atm, but you can see a "demo" on gabrielfalcao/lettuce here.