docs: follow-up plans for template-inheritance gaps - #65
Merged
Conversation
Three plans addressing the gaps surfaced by the question of how reusable workflows propagate from this repo through `<owner>/.github` to consumer repos: 1. bulk-install-smartwatermelon-fleet — workaround for the fact that `smartwatermelon` is a user account, so workflow-templates never appear in the picker UI for `smartwatermelon/*` repos. Script-based opt-in install across the existing fleet. 2. create-nightowlstudiollc-github-defaults — stand up the org's `.github` repo so workflow-templates do work for new repos in that org, plus mirror community defaults. 3. required-workflows-nightowlstudiollc — force-enforcement via Repository Rulesets (GitHub deprecated the standalone Required Workflows feature in 2023; Rulesets are the live mechanism). Audit-only first, escalate to active. Plans cross-reference each other and call out the order/dependency between them. Smartwatermelon→org migration is explicitly out of scope per current direction. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
Three plans addressing the question raised in this session: how do reusable workflows here propagate through
<owner>/.githubto consumer repos? The investigation surfaced two structural facts and three independent gaps to close.The facts:
smartwatermelonis a user account, not an org. GitHub'sworkflow-templates/picker is org-only, so theworkflow-templates/directory insmartwatermelon/.githubnever surfaces in any UI.nightowlstudiollcIS an org (team plan), but has no.githubrepo yet, so it inherits no defaults at all.The plans:
bulk-install-smartwatermelon-fleet— script-based workaround for smartwatermelon, since workflow-templates won't ever auto-propagate there.create-nightowlstudiollc-github-defaults— stand upnightowlstudiollc/.githubso the picker works for new repos in that org.required-workflows-nightowlstudiollc— force-enforcement via Repository Rulesets. (GitHub deprecated standalone Required Workflows in 2023 in favor of Rulesets — got that wrong in my first draft, corrected before commit.)Cross-references between plans are wired up. Order of execution would be 2 → 1 → 3, with 3 in audit-only mode for a calibration window before activation.
The companion fix to
smartwatermelon/.github/workflow-templates/claude-blocking-review.yml(bumping the stale@v2.0.1pin to@v3.0.0) is in flight at smartwatermelon/.github#7.Test plan
🤖 Generated with Claude Code