Repository navigation
fix: disable canary issues creation (#3119) - #3134
Merged
Merged
Conversation
* fix: disable canara issues creation * ci: re-trigger regression-test-check after adding skip-regression-check label
Contributor
|
Note Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported. |
github-actions
Bot
added
size: M
Contributor
There was a problem hiding this comment.
Pull request overview
Disables automatic GitHub issue creation for failures in the scheduled Live Canary GitHub Actions workflow, reducing side effects/noise from canary runs.
Changes:
- Remove
issues: writeworkflow permission. - Remove per-lane “Open failure issue” steps that created GitHub issues on scheduled failures.
- Force
CANARY_CREATE_ISSUESto"0"for the Slack notifier job to prevent issue creation paths.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Comment on lines
777
to
781
| CANARY_RUN_URL: ${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }} | ||
| GITHUB_SHA: ${{ github.sha }} | ||
| # Reuse the same PAT auth-live-canary uses for GitHub | ||
| # fixture access; it's already scoped for nearai/ironclaw | ||
| # work and avoids minting a new secret. CANARY_ISSUES_TOKEN | ||
| # has priority over GH_TOKEN / GITHUB_TOKEN inside the | ||
| # notifier (see scripts/live-canary/notify_slack.py | ||
| # `--github-token` precedence). | ||
| CANARY_ISSUES_TOKEN: ${{ secrets.AUTH_LIVE_GITHUB_TOKEN }} | ||
| GITHUB_REPOSITORY: ${{ github.repository }} | ||
| # Only auto-open issues for scheduled runs — manual | ||
| # workflow_dispatch tests would otherwise flood the tracker | ||
| # while iterating on canary changes locally. | ||
| CANARY_CREATE_ISSUES: ${{ github.event_name == 'schedule' && '1' || '0' }} | ||
| CANARY_CREATE_ISSUES: "0" | ||
| run: | |
theredspoon
pushed a commit
to theredspoon/ironclaw
that referenced
this pull request
Jun 21, 2026
* fix: disable canara issues creation * ci: re-trigger regression-test-check after adding skip-regression-check label Co-authored-by: Nick Pismenkov <50764773+nickpismenkov@users.noreply.github.com>
This branch had an error being deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
fix: disable canara issues creation
ci: re-trigger regression-test-check after adding skip-regression-check label
Summary
Change Type
Linked Issue
Validation
cargo fmt --all -- --checkcargo clippy --all --benches --tests --examples --all-features -- -D warningscargo buildcargo test --features integrationif database-backed or integration behavior changedreview-prorpr-shepherd --fixwas run before requesting reviewSecurity Impact
Database Impact
Blast Radius
Rollback Plan
Review Follow-Through
Review track: