If we do use "feature/..." as the branch naming convention, it does pose an
issue with the patch naming due to the separator character ('/'). How about
"feature-..."?On Tue, Nov 10, 2015 at 3:02 PM, Anu Engineer <aengin...@hortonworks.com> wrote: > I ran into the same issue and filed an INFRA jira too. > > https://issues.apache.org/jira/browse/INFRA-10720 > > > So +1 for having the git control back > > Thanks > Anu > > > > > > On 11/10/15, 2:45 PM, "Steve Loughran" <ste...@hortonworks.com> wrote: > > > > >> On 10 Nov 2015, at 22:07, Karthik Kambatla <ka...@cloudera.com> wrote: > >> > >> Hi folks, > >> > >> Recently, Infra disabled force-pushes (and non-fast-forward pushes) to > all > >> branches to avoid accidental overwrites or deletions. > >> > >> I propose we reach out to Infra and ask for an exemption since our > workflow > >> for feature branches involves deletions and force-pushes. > >> > > > >I asked them for this exemption for all branches called feature/* earlier > today; its consistent with the git flow branch naming. > > > >if all feature branches go in under there, people working on them are > free to rebase as they choose. > > > >> We should likely wait for a day or so to hear any concerns against this > >> request. Also, can someone volunteer following up on this? I am going > away > >> on vacation shortly, and will have limited access to internet/email. > >> > > > > > > >
