chore(governance): auto-seed org templates from Quantum-L9/.github - #228
chore(governance): auto-seed org templates from Quantum-L9/.github#228cryptoxdog wants to merge 1 commit into
Conversation
|
❌ 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: 2c7929a72a
ℹ️ 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.
In the inspected l9-lint-test-node.yml, both typecheck and test run on every pull request and push, but a repo-wide manifest search found no package.json or Node lockfile. Consequently this fallback executes bare npm install, which exits with ENOENT because there is no package.json, making both jobs fail before their intended skip checks; the npm documentation defines bare npm install as operating in a package directory and installing dependencies listed in package.json. Remove this Node-specific workflow or condition the jobs on a manifest being present.
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 branch is always taken: a repo-wide search including hidden and ignored files found no sync_ci_from_pack.py, only these workflow references. The job therefore exits successfully without syncing anything or creating the promised PR, so future organization-template updates are silently discarded; seed the implementation alongside this receiver or invoke a centrally available sync action instead.
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 the sync operation introduces a new template rather than modifying a tracked file, bare git diff --quiet reports no difference because it does not include untracked paths, so changed=false prevents the subsequent git add -A and PR creation. The git diff documentation describes the no-argument form as comparing the working tree with the index; use a status check that includes untracked files before deciding to skip the PR.
Useful? React with 👍 / 👎.
| ## This Repo's Own CI | ||
|
|
||
| `Quantum-L9/.github` validates itself on every PR/push to `main` — note that | ||
| none of the 12 files under `workflow-templates/` ever run as CI *in this | ||
| repo*; they only appear as starter-workflow choices in other repos' Actions | ||
| tab. What actually executes here: |
There was a problem hiding this comment.
This section identifies the current repository as Quantum-L9/.github and documents CI over workflow-templates/, l9-ci-pack/, .github/workflows/actionlint.yml, and ops/audit-sha-pins.sh, but none of those paths exist in the inspected CEG tree. Contributors are therefore directed to validate an unrelated repository instead of this Python engine's actual Ruff, mypy, pytest, and contract-scanner gates; adapt the guide to CEG before publishing it.
AGENTS.md reference: AGENTS.md:L16-L19
Useful? React with 👍 / 👎.
d6ebb7b to
9ca0d74
Compare
9ca0d74 to
6d328b9
Compare
|
|
Closing: org auto-seed PR is known-broken (fails CI) and is noise. Do not re-open from the seeder until the template is fixed. |
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.