I dont think its possible, I also dont see anything on that, suggesting playing with local symbolic refs is as close as you can get. Which probably makes sense given how it works.
I haven't tried this myself yet, but in another project (non-ASF) mention was made that GitHub said to do the below locally after they had renamed from "master" to "main". I believe they probably did the rename using GitHub's tooling, which we won't, and so this may not be as applicable...but seems like it should be: git branch -m master main git fetch origin git branch -u origin/main main (Where origin is the repo remote name, so you might replace that if you are using something else as its remote) Potentially one could use the above to locally rename the branch too, and then also if desired the symbolic-ref trick just to catch any accidental (or otherwise) mentions of master, and so actually end up on "main" instead. On Thu, 11 Mar 2021 at 15:54, Clebert Suconic <[email protected]> wrote: > > I need a little help as google failed me.. (or perhaps I just want to > make sure there is no way to do this). > > I looked around and there is a way to create a symlink in git: > > git symbolic-ref refs/heads/master refs/heads/main > > However the symbolic-ref will only exist locally on my git. > > does anyone know a way to make this link to be "committed" on gerrit, > and perhaps how to delete it later on. > > > I could only find a way to do it locally. Anyone have any idea? > > On Thu, Mar 11, 2021 at 10:34 AM Clebert Suconic > <[email protected]> wrote: > > > > Thanks a lot, I have everything I need now > > > > I plan to work on this next week.. I will follow up with progress as I > > go over this thread. > > > > On Wed, Mar 10, 2021 at 6:24 AM Robbie Gemmell <[email protected]> > > wrote: > > > > > > Yep, thats the only config we have for the website auto build, which > > > is a standard build. Essentially we just enable it and tell it which > > > branch to build changes from (the one matching whoami) and then the > > > target branch to commit and push any output updates to, where they are > > > then picked up from for the web servers. > > > > > > The build itself occurs on a Builtbot CI instance at > > > https://ci2.apache.org/#/builders/7. A mail is sent on each build to > > > commits@, e.g the latest one is: > > > https://lists.apache.org/thread.html/rc14442fcfba8395bec5207f2c43b8dbde068f369fabe50de039509fc%40%3Ccommits.activemq.apache.org%3E > > > > > > On Tue, 9 Mar 2021 at 22:46, Justin Bertram <[email protected]> wrote: > > > > > > > > The website actually uses Jekyll. The branch it uses is controlled via > > > > the > > > > .asf.yaml file [1]. More details about this are here [2]. > > > > > > > > > > > > Justin > > > > > > > > [1] https://github.com/apache/activemq-website/blob/master/.asf.yaml > > > > [2] > > > > https://cwiki.apache.org/confluence/display/INFRA/git+-+.asf.yaml+features#Git.asf.yamlfeatures-JekyllCMS > > > > > > > > On Tue, Mar 9, 2021 at 4:42 PM Clebert Suconic > > > > <[email protected]> > > > > wrote: > > > > > > > > > I see the website is the pelican system. > > > > > > > > > > I'm not sure how the AMQ5 is configured on Jenkins... that's the only > > > > > thing > > > > > I'm lost now. > > > > > > > > > > > > > > > > > > > > On Tue, Mar 9, 2021 at 4:31 PM Clebert Suconic > > > > > <[email protected]> > > > > > wrote: > > > > > > > > > > > That's right.. I will do it for all the Branches... > > > > > > > > > > > > > > > > > > At this point now I'm looking to what I would need to change on > > > > > > ci-builds > > > > > > > > > > > > > > > > > > I'm looking on ci-builds for things we would need to change.. > > > > > > > > > > > > however I don't understand how ActiveMQ5 is configured here: > > > > > > > > > > > > https://ci-builds.apache.org/job/ActiveMQ/job/ActiveMQ/ > > > > > > > > > > > > > > > > > > I could find the simple configuration on artemis, but AMQ5 is using > > > > > > some fancy configuration that I don't know where it's taking it > > > > > > from. > > > > > > > > > > > > @Jb or anyone can you give me some pointers here? I'm really curious > > > > > > now.. (I know you could say you would change it. .but at this point > > > > > > I'm trying to understand what is going on :) ) > > > > > > > > > > > > > > > > > > Also: where is the build for the website? I can't find it on > > > > > > ci-builds.apache.org > > > > > > > > > > > > On Tue, Mar 9, 2021 at 3:10 AM Jean-Baptiste Onofre > > > > > > <[email protected]> > > > > > > wrote: > > > > > > > > > > > > > > That’s my guess as well ;) > > > > > > > > > > > > > > > Le 9 mars 2021 à 08:57, michael.andre.pearce < > > > > > > [email protected]> a écrit : > > > > > > > > > > > > > > > > I assume the plan is to cover all repos, not just artemis.Sent > > > > > > > > from > > > > > my > > > > > > Galaxy > > > > > > > > -------- Original message --------From: Clebert Suconic < > > > > > > [email protected]> Date: 06/03/2021 14:33 (GMT+00:00) To: > > > > > > [email protected] Subject: Re: [DISCUSS] Renaming master as > > > > > > main > > > > > We > > > > > > will have to create the main branch on gitbox and Infra will make > > > > > theswitch > > > > > > on GitHub.On Sat, Mar 6, 2021 at 12:15 AM Jean-Baptiste Onofre < > > > > > > [email protected]>wrote:> Correct, we should focus on gitbox > > > > > > (that’s why > > > > > > better to ask to infra).>> Regards> JB>> > Le 5 mars 2021 à 23:16, > > > > > > Justin > > > > > > Bertram <[email protected]> a écrit :> >> > Aren't the Apache > > > > > > GitHub > > > > > > repos just mirrors of the official versions on> > Apache's > > > > > infrastructure? > > > > > > I know when we merge PRs we push to> > https://gitbox.apache.org/. > > > > > > If > > > > > the > > > > > > GitHub repo is just a mirror> wouldn't we> > have to rename the > > > > > > branch on > > > > > > Apache first? I'm not real clear on all the> > details of how the > > > > > > integration works so maybe that's wrong.> >> >> > Justin> >> > On > > > > > > Fri, > > > > > Mar > > > > > > 5, 2021 at 4:06 PM Matt Pavlovich <[email protected]>> wrote:> >> > > > > > > >> > > > > > > GitHub solved the PR move if the rename is done via their UI:> >>> > > > > > > >> > > > > > > https://github.com/github/renaming > > > > > > <https://github.com/github/renaming>> > > > > > > >>> >> -Matt> >>> >>> On Mar 5, 2021, at 2:54 PM, Clebert Suconic < > > > > > > [email protected]> >> >> wrote:> >>>> >>> Good point.> >>>> > > > > > > >>> > > > > > > I’m not sure what to do with pending PRs> >>>> >>> In artemis you > > > > > > could > > > > > use > > > > > > the scripts and they would work.> >>>> >>> On Fri, Mar 5, 2021 at > > > > > > 2:54 PM > > > > > > Matt Pavlovich <[email protected]>> >> wrote:> >>>> >>>> +1 no > > > > > > problem. > > > > > > Please to cover the CI jobs, so we don’t lose those.> >>>> Thanks!> > > > > > > >>>>> > > > > > > >>>>> On Mar 5, 2021, at 11:24 AM, Clebert Suconic <> >> > > > > > > [email protected]>> >>>> wrote:> >>>>>> >>>>> I would like > > > > > > to > > > > > > propose to rename all of our git branches as main on> >>>>> all of > > > > > > our > > > > > > branches. This would be a very first easy step to take on> >>>>> > > > > > > renaming > > > > > > offensive language from our codebases.> >>>>>> >>>>> We could allow > > > > > > some > > > > > > time before we do that, say 7 days after we> decide> >>>>> to take > > > > > > the > > > > > > move.> >>>>>> >>>>> Anyone sees a problem with that?> >>>>>> >>>>> > > > > > > if > > > > > > anyone has internal forks depending on master (say if you have a> > > > > > > >>>>> > > > > > > downstream branch of ActiveMQ), you will likely have to update your> > > > > > >>>>> > > > > > > internal git repos and scripts.> >>>>>> >>>>> We could keep the > > > > > > master > > > > > for > > > > > > some time without being updated, until> we> >>>>> remove it later.> > > > > > > >>>>> > > > > > > >>>> --> >>> Clebert Suconic> >>> >>>> --Clebert Suconic > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > Clebert Suconic > > > > > > > > > > > > > > > > > > > -- > > Clebert Suconic > > > > -- > Clebert Suconic
