label for contracts artifact release workflow to run before merge#642
label for contracts artifact release workflow to run before merge#642vicentevieytes wants to merge 2 commits intomainfrom
Conversation
|
👋 vicentevieytes, thanks for creating this pull request! To help reviewers, please consider creating future PRs as drafts first. This allows you to self-review and make any final changes before notifying the team. Once you're ready, you can mark it as "Ready for review" to request feedback. Thanks! |
There was a problem hiding this comment.
Pull request overview
Updates the TON contracts compiled-artifacts publishing workflow so it can be explicitly opted into on pull requests via a label, while preserving existing behavior for main pushes and manual dispatch runs.
Changes:
- Add
pull_requestevent types to includelabeled(and explicitly list existing default PR actions). - Gate the
publishjob on PRs behind thebuild-publish-contractslabel (while still requiring relevant contract/workflow changes or a manual dispatch).
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| pull_request: | ||
| types: [labeled, opened, synchronize, reopened] |
There was a problem hiding this comment.
With pull_request triggering on opened/synchronize/reopened (plus labeled), the workflow will still run the changes job for PRs that don’t have the build-publish-contracts label, even though publish will be skipped. If the intent is to only spend CI time when the label is present, consider adding a similar label-gated if: to the changes job (or otherwise gating early), so the workflow no-ops quickly on unlabeled PR events.
No description provided.