Conversation
The organization-level auto-add-to-project workflow fires on every issue and PR opened across all wyre-technology repos. When PROJECT_TOKEN isn't available (org secret not set, or not exposed to a given repo), the action fails with: Input required and not supplied: github-token That shows up as a red X on every PR across ~38 MCP repos, making it impossible to distinguish real check failures from this infra gap. This change adds a pre-step that checks whether PROJECT_TOKEN is set: - If set → workflow runs as before and adds the item to the project - If not set → workflow emits a ::notice and exits successfully Effect: - Adding PROJECT_TOKEN later (org secret or repo secret) "just works" without further changes — the check flips on automatically. - All MCP-repo PRs stop showing the spurious failure today. Pattern is injection-safe: only secrets.PROJECT_TOKEN is referenced, passed via env: rather than string interpolation into the shell.
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
1 participant
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
Unblocks every PR across all wyre-technology repos (~38 MCP repos) from showing a spurious red X on the `add-to-project` check.
Problem
The org-level `auto-add-to-project.yml` workflow fires on every issue and PR. When `PROJECT_TOKEN` isn't available — either because the org secret isn't set or isn't exposed to a given repo — the action fails with:
```
Input required and not supplied: github-token
```
That shows up as a red X on every PR, drowning out real check failures. Seen today on connectwise-manage-mcp#9 among others.
Fix
Adds a pre-step that checks whether `PROJECT_TOKEN` is set before invoking `actions/add-to-project`:
This means adding `PROJECT_TOKEN` later (org secret or repo-scoped secret) "just works" — no further workflow changes needed.
Security
The check uses the injection-safe pattern:
Test plan