Just another piece of gem that I know if is that if your feature branch name is in lowercase, commits there don't generate jira comments.
On Wed, 20 Nov, 2019, 3:02 AM Michael Sokolov, <msoko...@gmail.com> wrote: > got it, thanks! > > On Tue, Nov 19, 2019 at 4:10 PM Dawid Weiss <dawid.we...@gmail.com> wrote: > > > > > Hoss said branches must be named starting jira/, but I'm not familiar > > > with this convention. > > > > This convention is merely so that when you do "git branch -r" the > > branches displayed are sorted and presented in some sane order > > (because of prefixes). > > > > > If we follow that, can we use github to coordinate PR's against a > feature branch among > > > multiple developers? > > > > If you create a branch with a prefix and somebody forks the project > > and then creates a pull request then it's still going to be against > > that prefixed branch (read: I don't see the problem?). > > > > Branches are just labels attached to a commit. Nothing special about > > the slash character (I believe). > > > > > > D. > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > > For additional commands, e-mail: dev-h...@lucene.apache.org > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: dev-h...@lucene.apache.org > >
