ANNOUNCE: [GNC-dev] Repository Branch Changes

[john]

Docs: Yes, as it would be confusing to have different branch names in code and doc.

Accidental pushes: I'm looking into that. I think I can do that in the post-commit hook.

Wiki articles: Thanks for the reminder.

Regards,
John Ralls


> On Mar 26, 2023, at 8:36 PM, David T. via gnucash-devel <gnucash-devel at gnucash.org> wrote:
> 
> Out of idle curiosity (since I'm not actively working on these things any more), are these changes applying to the docs platform as well? 
> 
> And are there mechanisms that can prevent the sporadic developer who might have an existing clone locally from pushing to these outdated branches? I imagine that there are many clones out there in the hands of such intermittent developers.
> 
> Also, ISTR that there are extensive instruction guides to development on the wiki. I'll hope that those will get appropriate updates to reflect the new naming conventions...
> 
> ⁣David T. ​
> 
> On Mar 27, 2023, 2:54 AM, at 2:54 AM, John Ralls <jralls at ceridwen.us> wrote:
>> I've created new `stable` branches in gnucash.git and gnucash-docs.git
>> and changed Github's default branch to them. This is effectively a
>> rename of master; when Derek has time he'll delete the master branches
>> from code and Github.
>> 
>> You can modify your local repositories with:
>> git branch -D maint
>> git branch -m master stable
>> git fetch origin
>> git branch -u origin/stable stable
>> git remote set-head origin -a
>> 
>> and optionally to clean things up:
>> git remote prune origin
>> 
>> Please do this ASAP to avoid inadvertently pushing anything to maint or
>> master!
>> 
>> Regards,
>> John Ralls
>> 
>> _______________________________________________
>> gnucash-devel mailing list
>> gnucash-devel at gnucash.org
>> https://lists.gnucash.org/mailman/listinfo/gnucash-devel
> _______________________________________________
> gnucash-devel mailing list
> gnucash-devel at gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-devel