chore: add auto-add to engineer kanban workflow#5
Merged
LukasWodka merged 2 commits intodevelopfrom Apr 25, 2026
Merged
Conversation
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
@v1 is not a valid tag — action publishes full semver only. Pin to v1.0.2. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Contributor
Author
|
Re-triggering workflow after v1.0.2 pin. |
saadqbal
approved these changes
Apr 24, 2026
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
2 participants
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.
Summary
Adds a 14-line GitHub Actions workflow that auto-adds every new issue and pull request from this repo to the engineer kanban project:
→ https://github.com/orgs/tracebloc/projects/2
Fires on
issues: opened|reopened|transferredandpull_request: opened|reopened|ready_for_review. No effect on existing items.Why
GitHub Projects v2's built-in "Auto-add to project" workflow only supports one repo per project. This action-based approach is GitHub's recommended workaround to get cross-repo visibility on a single kanban.
Dependencies
Uses the org-level secret
PROJECTS_KANBAN_TOKEN(already configured withproject+reposcopes, visible to all repositories).Testing
After merge, open any new issue or PR and confirm it appears in the
Backlogcolumn of the kanban within a few seconds. If it doesn't, check the Actions tab for the workflow run.Related
One of ~18 identical PRs being rolled out across the tracebloc org so every repo's work lands on the shared engineer kanban.
🤖 Generated with Claude Code