I've cleaned up the offending branches below. In general, we should be careful about how we use Github to merge in our work. I'm not sure how these branches were created. In general, you should not need to use "Merge" to merge your work in. Either Rebase (in the case of 1 commit) or "Squash and Merge" (in the case of multiple commits) is enough.
If you do an action through Github like a Revert, please double check that you have not created a branch in origin. On 4/11/18, 10:37 AM, "Jonathan Hurley" <[email protected]> wrote: Hi committers, It looks like we have some rogue branches showing up again (perhaps the result of our trial and error with the new pull request model). In any event, here are the branches I am nominating for removal. If you don't want one of these removed, please respond to this email: AMBARI-22815-branch-feature-AMBARI-14714 AMBARI-22945-branch-feature-AMBARI-14714 AMBARI-22957-branch-feature-AMBARI-14714 AMBARI-22868-branch-2.5 AMBARI-22868-branch-2.6 AMBARI-22868-trunk my_trunk revert-610-branch-feature-AMBARI-14714-ui vbrodetskyi-branch-2.6
