peezy-tech/patch-moi-harness
2
0
Fork
You've already forked patch-moi-harness
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
Tiny npm package harness for patch.moi fork maintenance tests
9 commits 2 branches 4 tags 47 KiB
  • JavaScript 100%
Find a file
Exact
Repository files (latest commit first)
Filename Latest commit message Latest commit date
matamune 9fd9d8c31a
 Add fork package release identity
2026-05-16 04:13:10 +00:00
.github/workflows Add fork package release identity 2026-05-16 04:13:10 +00:00
bin Add maintained fork shout mode 2026-05-16 03:44:22 +00:00
src Add fork package release identity 2026-05-16 04:13:10 +00:00
test Add maintained fork shout mode 2026-05-16 03:44:22 +00:00
.gitignore Initial patch.moi harness package 2026-05-16 03:28:45 +00:00
LICENSE Initial patch.moi harness package 2026-05-16 03:28:45 +00:00
package-lock.json Add fork package release identity 2026-05-16 04:13:10 +00:00
package.json Add fork package release identity 2026-05-16 04:13:10 +00:00
README.md Add fork package release identity 2026-05-16 04:13:10 +00:00

README.md

patch-moi-harness fork

Tiny releaseable npm package used to exercise patch.moi fork maintenance.

The repository is intentionally small so patch.moi can iterate quickly against the whole maintenance loop:

  • GitHub peezy-tech/patch-moi-harness is the upstream release surface.
  • GitHub matamune-peezy/patch-moi-harness is the fork release surface.
  • The maintained fork carries a small patch stack on top of upstream.

Usage

npx @peezy.tech/patch-moi-harness-fork patch.moi

import { buildInfo, greet } from "@peezy.tech/patch-moi-harness-fork";

console.log(greet("patch.moi"));
console.log(buildInfo());

Release

Releases are tag-driven:

git tag fork-v0.1.3-fork.0
git push github-fork main fork-v0.1.3-fork.0

The npm trusted publisher should be configured for:

  • Package: @peezy.tech/patch-moi-harness-fork
  • GitHub organization/user: matamune-peezy
  • GitHub repository: patch-moi-harness
  • Workflow filename: publish.yml
  • Environment: npm-publish