feat(org-config): wire add-to-project into org-sync#9
Merged
bitwise-fast-forward-merge[bot] merged 3 commits intoJul 1, 2026
Merged
Conversation
Contributor
|
Note Merging this PR: this repository merges by fast-forward so every The branch must be up to date with |
tiffanywang3
previously approved these changes
Jul 1, 2026
Collaborator
Author
|
/auto-merge |
bitwise-fast-forward-merge
Bot
added
the
auto-merge
Contributor
|
Note Auto-merge armed. Once this PR is approved and every required check Remove the |
Contributor
|
Cannot
|
Add a `workflows-sync` command that fans repo-config/workflows/*.yaml out to .github/workflows/ in every non-archived org repo via the Contents API — upsert only (never deletes), idempotent (skips byte-identical files), with a Signed-off-by trailer. In the same pass it links the shared Roadmap project onto each repo with `gh project link` (skipping repos already linked) so the board also shows on the repo's Projects tab, and backfills each repo's existing issues into the project with `gh project item-add` (ISSUE_STATE, default open; dedupes) so the board catches up on work opened before the workflow existed. Ship the canonical add-to-project caller it distributes: on `issues: opened` it calls the reusable github-workflows add-to-project workflow, adding the issue to the shared org Roadmap project so every repo's issues collect in one board. A Contents-API commit is unsigned (GitHub web-flow-signs only web-UI and GitHub App commits, not OAuth-token API writes), so pushing the caller to a public repo's protected default branch requires an org owner to bypass required_signatures and code_scanning; add OrganizationAdmin to the bypass_actors of public-release-branch-security and public-code-quality (pull_request is already bypassed) and apply with `org-config.sh import`. Closes bitwise-media-group#6 Signed-off-by: Deavon M. McCaffery <dmccaffery@users.noreply.github.com>
…ject The caller only triggered on `issues: [opened]`, so opened PRs never landed on the shared org Roadmap board. Add a `pull_request_target: [opened]` trigger. pull_request_target (not pull_request) so PRs opened from forks are captured too — a fork's pull_request event runs without secrets, which would fail the App-token mint. Safe here because the reusable workflow never checks out PR code; it only adds the item to the board. Existing repos keep the old trigger until the next `org-config.sh workflows-sync` re-pushes this caller; this fixes the canonical template so future syncs and newly created repos get it. Also add the standard `Copyright` / `SPDX-License-Identifier: MIT` header to the caller template, matching the org's reusable workflow files. Signed-off-by: Deavon M. McCaffery <dmccaffery@users.noreply.github.com>
Signed-off-by: Deavon M. McCaffery <dmccaffery@users.noreply.github.com>
dmccaffery
force-pushed
the
feat/add-to-project
branch
from
eeeb99f to
dab16c9
Compare
Contributor
|
Cannot
|
tiffanywang3
approved these changes
Jul 1, 2026
Contributor
|
Fast-forwarded |
bitwise-fast-forward-merge
Bot
merged commit dab16c9
into
bitwise-media-group:main
4 checks passed
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.
Add a
workflows-synccommand that fans repo-config/workflows/*.yaml out to .github/workflows/ in every non-archived org repo via the Contents API — upsert only (never deletes), idempotent (skips byte-identical files), with a Signed-off-by trailer. In the same pass it links the shared Roadmap project onto each repo withgh project link(skipping repos already linked) so the board also shows on the repo's Projects tab, and backfills each repo's existing issues into the project withgh project item-add(ISSUE_STATE, default open; dedupes) so the board catches up on work opened before the workflow existed.Ship the canonical add-to-project caller it distributes: on
issues: openedit calls the reusable github-workflows add-to-project workflow, adding the issue to the shared org Roadmap project so every repo's issues collect in one board.A Contents-API commit is unsigned (GitHub web-flow-signs only web-UI and GitHub App commits, not OAuth-token API writes), so pushing the caller to a public repo's protected default branch requires an org owner to bypass required_signatures and code_scanning; add OrganizationAdmin to the bypass_actors of public-release-branch-security and public-code-quality (pull_request is already bypassed) and apply with
org-config.sh import.Closes #6