Yeah, that was me, sorry. An issue with a misconfigured git remote. Anyways, it would be great if we could do an "allowBranches" instead of a "ignoreBranches". Because we only care about "branch_*x", "branch_*_*" and "main".
- Houston On Sun, Apr 20, 2025 at 7:00 PM David Smiley <dsmi...@apache.org> wrote: > Update: I think the current configuration is here: > > https://github.com/apache/infrastructure-p6/blob/production/modules/svngit2jira/templates/svngit2jira.cfg.erb > I see we can start a branch with "feature", which is a reasonable prefix. > Granted "feature" is often an inaccurate characterization of the branch but > whatever. > > On Mon, Apr 21, 2025 at 8:54 AM David Smiley <dsmi...@apache.org> wrote: > > > This is a reminder for those of us that might wish to create new > > branches. A couple days ago, a bunch of JIRA issues received a bot > comment > > to indicate that the JIRA issue in question has a commit on a new branch > > "add-pki-caching" (hello Sanjay!). These are annoying/unwelcome comments > > spamming JIRA and issues list. The trick/secret is to name the branch > > prefixed with "solr", and then it won't happen. I'll follow up with ASF > > Infra to get more info on this... the underlying configuration appears to > > have moved and we'd like another pattern nowadays anyway. > > > > On Wed, Mar 16, 2022 at 3:34 AM David Smiley <david.w.smi...@gmail.com> > > wrote: > > > >> > >> ~ David > >> > >> > >> ---------- Forwarded message --------- > >> From: David Smiley <david.w.smi...@gmail.com> > >> Date: Thu, Nov 21, 2019 at 9:27 AM > >> Subject: Re: feature branches > >> To: Solr/Lucene Dev <d...@lucene.apache.org> > >> Cc: java-dev <java-...@lucene.apache.org> > >> > >> > >> Yes; I'm partly responsible for that choice. Basically I want us to > >> standardize our branch names, and thus this feature of no noisy bot > >> comments pertaining to commits is exclusive to lowercase. What follows > is > >> my dev list post on this, which was agreed and not contested: > >> > >> (Early 2016) > >> --- > >> FYI as of March 15th (10 days now), commits to branches following the > >> pattern (lucene|solr).* (i.e. that which start with "lucene" or "solr") > >> will *not* get an automated comment on corresponding JIRAissues. All > >> others continue to. INFRA got this done for us: > >> https://issues.apache.org/jira/browse/INFRA-11198 > >> > >> I could have asked for a "jira" prefix too but leaving it this ways > >> encourages consistent branch naming that has been the most prevalent to > >> date. > >> > >> ~ David Smiley > >> Apache Lucene/Solr Search Developer > >> http://www.linkedin.com/in/davidwsmiley > >> > >> > >> On Tue, Nov 19, 2019 at 7:35 PM Ishan Chattopadhyaya < > >> ichattopadhy...@gmail.com> wrote: > >> > >>> 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 > >>>> > >>>> >
