Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updates build.yml trigger to automatically start workflow when a release branch is created #188

Merged
merged 1 commit into from
Aug 28, 2023

Conversation

michael-hawker
Copy link
Member

Our release process then just becomes create a branch off main named rel/major.minor.YYMMDD[-previewtag] like I did with 8.0.230823-rc.

This will then make it auto-trigger the workflow and wait to push to NuGet.org when an authorized maintainer signs-off on that step. (I had to manually start the workflow on the new branch for our first release.)

Only thing we need to do for minor/major versions is to update the directory props files ahead of that branch creation, which we should probably do along with whatever larger change we're planning to do or whatnot.

@michael-hawker michael-hawker added the enhancement New feature or request label Aug 24, 2023
@michael-hawker
Copy link
Member Author

Not sure why the CI failed here, some 400 error on artifact upload. Re-running.

@michael-hawker michael-hawker merged commit fce914d into main Aug 28, 2023
9 checks passed
@delete-merged-branch delete-merged-branch bot deleted the llama/build-on-release branch August 28, 2023 23:41
@michael-hawker
Copy link
Member Author

Thought for a second I had to look into the created event or something, but was just a bit delayed. Action spun up automatically when creating a new branch on GitHub, super simple for us to trigger a release now. Final bit to test will just be having a package without any preview tag at the end...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants