Make visible the reason for creation of new branch when conflicts with original branch are detected

pantheon-systems / quicksilver-pushback

Push any commits made on the Pantheon dashboard back to the original GitHub repository.

MIT License

14 stars 13 forks source link

Make visible the reason for creation of new branch when conflicts with original branch are detected #7

Open stevector opened 6 years ago

stevector commented 6 years ago

In preparation for a webinar last week I was working in the branch enabling-modules in this repo:

https://github.com/stevector/spooky-performance/branches

In making multiple commits on multidev, I saw at least two instances where new branches were created: 8ba7eenabling-modules and a1dc9enabling-modules.

@greg-1-anderson, have you ever seen this behavior where hashes get concatenated on to the branch name?

greg-1-anderson commented 6 years ago

This is caused by conflicts. Ideally, a new pull request, or at least a comment on the existing PR linking to the new branch should be added. This feature has not been done.

stevector commented 6 years ago

Thanks! I've updated the issue title and tags accordingly.