[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [sarif] RE: [EXTERNAL] Re: [sarif] Re: SARIF repository primary branch is now 'main'
Yes, Stefan, certainly we should discuss this, sorry for racing ahead. The context here is that Iâm trying to finalize the schema for our errata release. I do not want this schema to refer to our âmasterâ branch and propose that we update it to reference âmainâ.
There is a clear trend industry-wide to make this change and I definitely do think we should align with that.
Adityaâs suggestion is great, I was not aware that renaming in this way was required to provide the compatibility option, important information.
Unfortunately, I donât have sufficient permissions to rename the default âmasterâ branch to âmainâ, perhaps Chet Ensign does.
In any event, as per Stefanâs appeal, we can discuss as a group on Thursday. I will plan to finalize the errata schema optimistically referencing âmainâ: doing this wonât commit us to anything immediately, however, as we have other docs work to do there.
MCF
From: sarif@lists.oasis-open.org <sarif@lists.oasis-open.org> On Behalf Of Aditya SharadSent: Tuesday, July 12, 2022 10:30 AMTo: David Keaton <dmk@dmk.com>Cc: sarif@lists.oasis-open.orgSubject: [EXTERNAL] Re: [sarif] Re: SARIF repository primary branch is now 'main'
Sharing in case this helps before we discuss in person: GitHub now allows you to rename the existing `master` branch to `main`, rather than making a copy named `main`. If you do this, it will update most references, PRs, and links automatically, though local clones will still need to be updated manually.
Here are the GitHub docs on the topic: https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch
On Tue, Jul 12, 2022 at 9:46 AM David Keaton <dmk@dmk.com> wrote:
I will add this discussion to the agenda.Since the industry in general is moving from master to main, it isa good idea to align with current practice, though there may be variousideas about how to migrate.DavidOn 2022-07-12 09:39, Stefan Hagen wrote:> Hi,>> should we talk about such actions beforehand in the TC meeting? I would> prefer that.>> Question from which branch should I best branch off to create the new> minutes draft for the meeting on Thursday?>> â and to which branch should I target the pull request we use for the> live document before and during the meeting?>> Thanks,> Stefan>> On Tue, Jul 12, 2022, at 18:23, Michael Fanning wrote:>>>> Iâve created a copy of our current âmasterâ branch into the new>> primary development branch âmainâ.>>>>>> I **think** that GitHub will automatically redirect URL references>> from âmasterâ to âmainâ, when appropriate. This should mean that any>> existing references to our checked in schemata continue to work (see>> below for an example).>>>>>> I intend to test this soon by deleting the master branch and verifying>> these URLs still resolve. I wanted to give everyone here a heads up>> first, though, so people have a chance to switch over to âmainâ.>>>>>> MCF>>>>>>>>>> After our errata update, the link above will be rendered as.>> Hopefully, previous references to the link above will continue to work>> after I delete the âmasterâ branch. If thatâs not correct, we will>> retain the schemata in an archived âmasterâ branch.>>>>>>>---------------------------------------------------------------------To unsubscribe from this mail list, you must leave the OASIS TC thatgenerates this mail. Follow this link to all your TCs in OASIS at:
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]