-
Notifications
You must be signed in to change notification settings - Fork 13
Add a has-conflicts
badge to PRs automatically
#39
Comments
Maybe also add a comment to the PR letting the author/maintainers know that there are new conflicts that need to be resolved? I'm not sure exactly how this would work though. Would every open PR need to be checked for conflicts each time a commit is added to |
That's a good idea. But I'm 👎 on it as its only going to leave behind Off-topic comments that the maintainers will have to manually minimize.. Instead, I favor the silent labeling. We, the maintainers then shout-out to the author if we're not able to resolve the conflicts ourselves (either from lack of branch-access, or from lack of time, or from lack of the know-how to best proceed further..)
Yeah, that's how I vision it.. But how hard would it be for a Bot to traverse open PRs in reverse order and check for a conflict status from Github..? Definitely faster than a human doing the same, anyways.. 😛 |
👎 I'd rather minimize a comment than handle all conflicts. |
Probably that's how the rest of team feels as well.. 👍 |
According to https://developer.github.com/v3/repos/merging/ @jekyllbot could add a label if a merge returns a Maybe something to check in |
Yeah, checking if we get a 409 and adding some kind of |
GitHub status already reports a list of conflicts in a PR and disables
merge
as a consequence.It'd be better if JekyllBot could piggyback on that status and automatically add a
has-conflicts
label to such PRs or use Jekyll's existingpending-resolution
label.The text was updated successfully, but these errors were encountered: