Khan/actions

Letzte erfasste Quellaktivität: 3. September 2026 um 17:34

SkillsMP-Katalog aktualisiert: 2. November 2026 um 18:02

gesammelte Skills: 4

GitHub-Stars: 0
GitHub-Forks: 0

Mit einem KI-Assistenten installieren

Diesen Prompt kopieren und in den verwendeten KI-Assistenten einfügen.

Follow https://skillsmp.com/skill-install/prompt.md to install Agent Skills from https://github.com/Khan/actions.

README des Repositorys

README-Quelldatei: README.md

README-Quelldatei lesen

Vollständige README anzeigen

# @Khan/actions A monorepo for shared github actions. Currently only composite actions are supported, although supporting nodejs actions probably wouldn't be too hard. If your script is simple, you can do a composite action that uses `actions/github-script`, see the `filter-files` action for an example. ## How does the monorepo work? Github doesn't support putting actions in subdirectories, so we need to do some fancy work here. Inspired by [gitpkg](https://github.com/ramasilveyra/gitpkg), we "publish" versions of our actions to 'bare tags' in this repo. So the tag `filter-files-v0.0.1` would only contain the files for the `filter-files` action, and thus github is perfectly happy for us to reference it as `uses: @Khan/actions#filter-files-v0.0.1`. Actions that depend on other actions within this repo (with e.g. `uses: filter-files`) will have the references automatically converted to the appropriated pinned reference (e.g. `Khan/actions#filter-files-v0.0.1`) as part of the publish process. ## How does changeset play in? Changeset helps us track what needs to be published, and automatically produces a changelog, so we know what changed in a given release. ## How to Release New Action Versions - Make code changes. - Add changeset with `pnpm changeset`. Don't be alarmed that no other changesets exist. This changeset will be deleted by a following auto-generated PR after landing your PR by the [release workflow](./github/workflows/release.yml). - DO NOT update the package.json version or CHANGELOG.md for the action. It will be automatically updated by a following auto-generated PR after landing your PR by the [release workflow](./github/workflows/release.yml). An example PR generated by the release workflow can be viewed here: https://github.com/Khan/actions/pull/123/files ## How do I test just one action, before publishing? (Note [Lilli]: I don't know if there's a better way; this is just what I did.) Let's say I want to test a change to the `gerald-pr` action, pointed to from a different repo. I'm still working on it, so I don't want to publish it yet (as described above). I still need to get the action isolated in its own folder, outside the sub-folders of the monorepo. Here's what I did: 1. Find the last tagged-and-published version of that action (e.g., `gerald-pr-v0.0.1`). 2. Run `git checkout gerald-pr-v0.0.1` to create a detached HEAD. 3. Run `git checkout -b <branch-name>` to create a new branch with just those files. 4. Apply the changes to my development branch to this branch. Sometimes `git cherry-pick` can figure out the file-structure differences across branches. You can also manually create and apply patches. Or just manually bring in the changes, if they're small enough and you're careful enough. 5. Push the branch to the GitHub. 6. Point my other repo to my test branch with `uses: @Khan/actions@<branch-name>`. ## Testing the build and publish process All actions are built and "published" using the `utils/run-publish.ts` script. You can test almost all of it by running it and passing `--dry-run`. The only part that will be skipped is pushing each action's release git tags to Github. Example: ``` $ node -r @swc-node/register ./utils/run-publish.ts --dry-run ``` NOTE: The `--force` option can be used with `--dry-run` to simulate building and publishing even when there's no new tags to publish.

README des Repositorys wird geladen…

Skills in diesem Repository

Softwarequalitätssicherungsanalysten und -tester

1 Berufskategorien · 100% klassifiziert

Skill

Beruf

Beschreibung

Aktualisiert

review-consumer-bump

Softwarequalitätssicherungsanalysten und -tester

Bump the shared PR reviewer (`Khan/actions` `workflows/review`) pin, and optionally the autofix pin, in every consuming repo. One PR per consumer; a 3-way merge that preserves each repo's LOCAL OVERRIDE blocks; verification with the version-matched…

Quellsprache: Englisch

2026-09-03

review-feedback-audit

Softwarequalitätssicherungsanalysten und -tester

Audit the PR review workflow's posted output and human feedback in a consumer repo over a time window (typically since a reviewer deploy). Computes volume, verdict mix, label mix, verbosity, duplication at three grains, suppression notes, and human feedback…

Quellsprache: Englisch

2026-08-25

review-onboarding

Softwarequalitätssicherungsanalysten und -tester

Onboard a repo onto Khan's shared AI PR reviewer (`Khan/actions` `workflows/review`): install the workflow at a pinned tag, author the five consumer config files against that repo's own blast radius, validate the install with the consumer-config checker, and…

Quellsprache: Englisch

2026-08-25

review-trial

Softwarequalitätssicherungsanalysten und -tester

Run a seeded-defect live trial of the PR review workflow, comparing reviewer arms on isolated copies of one seeded PR (the Khan/webapp#40678 pattern). Use when evaluating an architecture-class review change, a re-review/lifecycle behavior change, or…

Quellsprache: Englisch

2026-07-31

Es werden 4 von 4 gesammelten Skills angezeigt.