See: https://cwiki.apache.org/confluence/display/INFRA/Git+workflow+for+infrastructure-puppet+repo
Gj On Mon, Sep 25, 2017 at 12:54 AM, Geertjan Wielenga < [email protected]> wrote: > Hi all, > > The Apache Way is to branch, rather than fork -- the idea being that via > branches, the code stays at Apache, rather than being somewhere else, i.e., > in someone else's Git repo. > > From the branch, reviews are done, prior to merging. > > We'll (I'll) also stop pushing straight to the ASF repo, i.e., was doing > this for batch license header changes -- and ended up including local OS > files, which I'm now fixing. > > So it appears that for everything we're doing its best and safest to > create a branch. > > Questions/comments welcome. > > Gj >
