-
Notifications
You must be signed in to change notification settings - Fork 773
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
Make publish workflow work based on tag/branch selected #3634
Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #3634 +/- ##
==========================================
- Coverage 87.35% 87.34% -0.01%
==========================================
Files 282 282
Lines 10132 10132
==========================================
- Hits 8851 8850 -1
- Misses 1281 1282 +1
|
This PR was marked stale due to lack of activity and will be closed in 7 days. Commenting or Pushing will instruct the bot to automatically remove the label. This bot runs once per day. |
This PR was marked stale due to lack of activity and will be closed in 7 days. Commenting or Pushing will instruct the bot to automatically remove the label. This bot runs once per day. |
Closing this in favor of #3638 |
Adds a
ref
parameter to the workflow that must be specified when running it. When running the workflow manually, specifying theref
is required. For our releases, we create both a "core" and "non-core" tag at the same SHA, and it doesn't matter which of the two tags you run the workflow with.Looks like this:
The nightly build will continue to use
main
.There is an alternative we could explore. The pack and publish workflow could be triggered when we draft a new release. If triggered this way, then the workflow would use the SHA of the release. No need to manually run the workflow and type in the tag name.