Skip to content

Conversation

@lbussell
Copy link
Member

Fixes #3179 and #3147.

With the parameters, you are able to specify any number of source and destination URLs and branches as well as what version to tag them as. At queue time you will need to edit the sdkVersion for each branch, as that determines the tags.

Further edits to the checklist, etc. are coming.

Typo

Formatting

Template expression formatting

Remove job name

try simpler case for debugging

Try different formatting

Try different formatting

Formatting and hosted images

More debugging, print json

Why are old variable names in my output

add back mirroring scripts

incorrect job and branch names

fix working directory

fully specify git directory

debug pat in url

use correct variable for url

debug url once again

no at sign in github urls

fix sed pattern

use pat

git push typo

try tagging

add git config name and email

combine scripts in case we fail early

Try follow tags

Try it on the real thing

production ready pool and branches
@ghost ghost added the area-additional-repos Adding additional contributing repos label Dec 16, 2022
@lbussell lbussell marked this pull request as ready for review December 17, 2022 00:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area-additional-repos Adding additional contributing repos

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Automatically tag releases in dotnet-security-partners/dotnet repo

3 participants