chore(governance): auto-seed org templates from Quantum-L9/.github - #230
chore(governance): auto-seed org templates from Quantum-L9/.github#230cryptoxdog wants to merge 1 commit into
Conversation
bd3d2d4 to
ee0bc9e
Compare
|
❌ PR Too Large 📋 Best Practices for Large Changes
🚫 This PR is blocked until reviewable size limits are met. |
L9 Audit Harness Report
Step Results
Architecture Audit Findings
See Spec Coverage
See Next StepsAll checks passed. Safe to merge. |
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
| @@ -0,0 +1,33 @@ | |||
| # Managed by Quantum-L9/.github. Pinned to a tag so main can move safely. | |||
| workflow_dispatch: | ||
|
|
||
| permissions: | ||
| contents: write |
| run: | | ||
| set -euo pipefail | ||
| case "${PACKAGE_MANAGER}" in | ||
| npm) if [ -f package-lock.json ]; then npm ci; else npm install; fi ;; |
| run: | | ||
| set -euo pipefail | ||
| case "${PACKAGE_MANAGER}" in | ||
| npm) if [ -f package-lock.json ]; then npm ci; else npm install; fi ;; |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: ee0bc9e661
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| run: | | ||
| set -euo pipefail | ||
| case "${PACKAGE_MANAGER}" in | ||
| npm) if [ -f package-lock.json ]; then npm ci; else npm install; fi ;; |
There was a problem hiding this comment.
Every pull request and push to main runs this job, but a repo-wide search finds no package.json or Node lockfile. The default npm branch therefore executes npm install in a directory without a package manifest, which exits with ENOENT; the duplicate install in the test job fails the same way, leaving otherwise valid Python changes with two consistently failing checks.
AGENTS.md reference: AGENTS.md:L16-L19
Useful? React with 👍 / 👎.
| if [ -f scripts/sync_ci_from_pack.py ]; then | ||
| python scripts/sync_ci_from_pack.py | ||
| else | ||
| echo "::notice::No sync_ci_from_pack.py found — skipping" | ||
| exit 0 |
There was a problem hiding this comment.
For every org_template_updated dispatch in this repository, this condition is false because a repo-wide search finds no scripts/sync_ci_from_pack.py or equivalent implementation. The step consequently succeeds without changing anything, the following diff check reports changed=false, and the advertised organization-template update never creates a PR.
Useful? React with 👍 / 👎.
| if git diff --quiet; then | ||
| echo "changed=false" >> "$GITHUB_OUTPUT" | ||
| else | ||
| echo "changed=true" >> "$GITHUB_OUTPUT" |
There was a problem hiding this comment.
When a future sync adds a template that did not previously exist, it will be untracked, and git diff --quiet ignores untracked files. This sets changed=false and skips the PR step even though there is a new file to publish; use a status check that includes untracked paths before deciding whether to create the sync PR.
Useful? React with 👍 / 👎.
PR remediation status — diagnosed, not remediated hereThis is #229 recreated by the auto-seeder on the same Blocked on a human — PR size
Blocked — the workflow this PR adds fails against this repo
Fix these upstream, not here The two remaining failures are in files this branch copies verbatim from
Patching them in this PR would be reverted by the next org update. The durable fix is in the template repo, after which the seed lands clean everywhere — not just here.
Tell me if you want the upstream template fixes raised in Generated by Claude Code |
0f76fdf to
17ee186
Compare
17ee186 to
341eaca
Compare
|
2 participants
Automatically seeds org template files from
Quantum-L9/.github/templates/plus thel9-ci-pack/Core hub.Files in this PR
.github/workflows/governance.yml.github/labels.ymlCODE_OF_CONDUCT.mdCONTRIBUTING.mdSUPPORT.md.github/FUNDING.yml.github/ISSUE_TEMPLATE/1-bug.yml.github/ISSUE_TEMPLATE/2-feature.yml.github/ISSUE_TEMPLATE/3-task.yml.github/ISSUE_TEMPLATE/4-incident.yml.github/ISSUE_TEMPLATE/bug_report.yml.github/ISSUE_TEMPLATE/ci-failure.yml.github/ISSUE_TEMPLATE/config.yml.github/ISSUE_TEMPLATE/feature_request.yml.github/ISSUE_TEMPLATE/gov-violation.yml.github/pull_request_template.md.github/workflows/on-org-update.yml.github/workflows/l9-lint-test-node.ymlbiome.json.biomeignore.vscode/extensions.jsonExisting files were left untouched (missing-only seed), except a stock ESLint
l9-lint-test-node.ymlwhich is replaced with the Biome SDK caller.Governance caller is advisory (
strictdefaults false).Core pack callers are distributed here;
l9-ci-coreexecutes CI.Opened automatically by Quantum-L9/.github auto-seed.