chore(governance): auto-seed org templates from Quantum-L9/.github - #42
chore(governance): auto-seed org templates from Quantum-L9/.github#42cryptoxdog wants to merge 1 commit into
Conversation
![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: a175e5dea3
ℹ️ 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".
| - name: Set up Node | ||
| uses: actions/setup-node@a0853c24544627f65ddf259abe73b1d18a591444 # v5.0.0 | ||
| with: | ||
| node-version: ${{ env.NODE_VERSION }} | ||
| cache: ${{ env.PACKAGE_MANAGER }} |
There was a problem hiding this comment.
On every pull request and push to main, both Node jobs enable setup-node's npm cache, but this commit contains no root package.json or supported lockfile (the only Node package is the nested router-shim/package.json). Consequently setup-node cannot resolve a dependency lockfile and fails before the intentionally optional type-check/test logic is reached, adding two consistently failing checks to this Python repository. Remove or guard this workflow, or configure it for the nested package with an appropriate lockfile.
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, the checked-in tree has no scripts/sync_ci_from_pack.py anywhere, so this branch exits successfully without fetching or updating any templates. The newly advertised auto-sync workflow is therefore permanently a green no-op; either seed the sync script, invoke an implementation from the source repository, or omit the receiver until an implementation is available.
Useful? React with 👍 / 👎.
165572e to
da9f02d
Compare
da9f02d to
e794775
Compare
|
1 participant
Automatically seeds org template files from
Quantum-L9/.github/templates/plus thel9-ci-pack/Core hub.Files in this PR
.github/CODEOWNERS.github/workflows/governance.yml.github/labels.ymlCODE_OF_CONDUCT.mdCONTRIBUTING.mdSECURITY.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.editorconfig.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.