Re: SARIF repository primary branch is now 'main'

["Stefan Hagen" <stefan@hagen.link>]

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

 

https://raw.githubusercontent.com/oasis-tcs/sarif-spec/master/Schemata/sarif-external-property-file-schema-2.1.0.json

 

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.

 

                https://raw.githubusercontent.com/oasis-tcs/sarif-spec/main/Schemata/sarif-external-property-file-schema-2.1.0.json