Skip to content

feat: establish org .github with reusable workflows and shared defaults - #1

Merged
00o-sh merged 1 commit into
mainfrom
claude/new-session-zrgq01
Aug 12, 2026
Merged

feat: establish org .github with reusable workflows and shared defaults#1
00o-sh merged 1 commit into
mainfrom
claude/new-session-zrgq01

Conversation

@00o-sh

@00o-sh 00o-sh commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

What & why

Centralizes the shared surface for the unabandoned maintained-fork program into this org
.github repo, so each fork can shrink to a thin caller plus its unique source instead of
duplicating six workflows and several config files apiece.

Reusable workflows (.github/workflows/reusable-*.yml)

Extracted from the merged events template, parameterized for per-fork variation:

  • reusable-ci — Node matrix (node-versions input), optional has-build step.
  • reusable-commitlint — Conventional-Commit PR linting.
  • reusable-publish — self-bootstrapping OIDC-or-token publish, hardened against
    the dev tree
    : no npm install unless install-for-publish: true, and --ignore-scripts
    on every publish. vars.OIDC_ENABLED / secrets resolve against the caller repo.
  • reusable-release-please — release-please + the "Dependencies & maintenance"
    changelog-fold post-step.
  • reusable-release-cut — monthly release merge (caller owns the cron).
  • reusable-release-security — CVE fast-path release.
  • reusable-codeql and reusable-scorecard — shared security scanning.

Org content

  • profile/README.md — org landing page (fork trigger, how to consume, how forks stay
    current).
  • CLAUDE.md — program guidance (prime directive, release model, secrets, fix-forward,
    attribution-footer + no-model-id rules, reusable-workflow layout).
  • Community-health filesSECURITY.md, CONTRIBUTING.md, SUPPORT.md, CODEOWNERS,
    bug-report + fork-request issue templates, PR template, FUNDING.yml.

Shared config

  • commitlint.config.js + .githooks/commit-msg (repo dogfoods its own reusable-commitlint).
  • templates/release-please-config.json — canonical changelog-sections block.
  • templates/README.md — copy-paste thin callers for standing up a new fork.
  • renovate.json with forkProcessing: enabled.

Type of change

  • feat — new shared infrastructure
  • ci — reusable workflows

Follow-ups (separate PRs)

The five forks convert to thin callers referencing these workflows at @main; those callers
will go green once this PR merges to main. The four heavy forks also migrate their test
suites onto built-in node:test to collapse their dev trees.


Generated by Claude Code

Centralize the shared surface for the unabandoned maintained-fork program so
each fork can shrink to a thin caller plus its unique source.

- reusable workflows: ci, commitlint, publish (OIDC-or-token, dev-tree
  hardened), release-please (changelog fold), release-cut, release-security,
  codeql, scorecard
- org profile README, CLAUDE.md program guidance
- community-health files: SECURITY, CONTRIBUTING, SUPPORT, CODEOWNERS,
  issue/PR templates, FUNDING
- shared config: commitlint config + githook, canonical release-please
  changelog-sections template, renovate.json (forkProcessing enabled)
- templates/ with copy-paste thin callers for new forks
@00o-sh
00o-sh merged commit 230ccae into main Aug 12, 2026
1 check passed
00o-sh added a commit to unabandoned/events that referenced this pull request Aug 12, 2026
* ci: replace workflows with thin callers to org reusable workflows

Each of the six workflows now calls the shared reusable workflow in
unabandoned/.github instead of carrying a full copy. Adds CodeQL and Scorecard
callers. Behaviour is unchanged (Node 20/22/24 matrix, OIDC-or-token publish,
monthly release-cut, CVE fast-path). Callers reference @main and go green once
unabandoned/.github#1 merges.

* ci: retrigger checks against merged reusable workflows

---------

Co-authored-by: Claude <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants