add prerelease branched to merge workflow #5388
Conversation
There was a problem hiding this comment.
Thoughts on renaming this workflow file to positron-merge-to-branch.yml now that it applies to any specified branches? We'd need to fix a reference to this file in .github/workflows/positron-pull-requests.yml if we go ahead with the rename. Not sure if there may be other places we'd want to update the filename?
For testing the changes, I had to backport the PR CI change to the prerelease/2024.11 branch in order for the CI changes to run against that branch. I'm going to backport #5352 to the other prerelease branches shortly.
We'll need to backport this PR to the prerelease branches too. The good news is that we'll be able to see if the merge to the prerelease branches kicks off the workflow right away!
|
Backporting this change to the prerelease branches:
|
Intent
Similar to #5352, we should run full test suite when merging to prerelease branches. This will help with catching issues when we aren't running the nightly full tests against the branch.
QA Notes
Tests run when merging to prerelease branch. This will be hard to test until a change to a prerelease branch is made.