- Notifications
You must be signed in to change notification settings - Fork1k
chore: pin dogfood to release branch during release freeze#20028
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
lgtm, will approve once you remove the testing checks
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
This reverts commit81ffde0.
6c2757d
tod2aa4cb
Comparee5c8c9b
intomainUh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Relates tohttps://github.com/coder/dogfood/pull/189
Closescoder/internal#1021
scripts/should_deploy.sh
which implements the algorithm in the linked issueci.yaml
workflow to run on release branchesci.yaml
into a new workflowdeploy.yaml
for concurrency limiting purposesmain-
prefixmain
branch will still push themain
andlatest
tagsrelease/x.y
branches will now pushrelease-x.y
tagsshould_deploy.sh
returns falsedogfood
TODO: