Repository navigation
feat: add github status, a report across an owner's repositories - #82
Merged
Merged
Conversation
`repokeeper github status [--owner <name>]` reads every repository of a user or
organization that is not archived (forks with --forks) and lists those that need
attention: open pull requests with their checks, open Dependabot alerts by severity
("off" when disabled), the latest finished run of each workflow on the default branch,
commits since the latest release tag, and a stale dependency graph.
The graph check compares the npm and NuGet versions of GitHub's SBOM with
package-lock.json, npm-shrinkwrap.json, pnpm-lock.yaml and packages.config on the
default branch, and reports a package the graph still names at a version the
lockfiles no longer contain; a commit touching the manifest makes GitHub re-read it.
--all lists every repository, --json prints the whole result, --exit-code exits 1
when something needs attention. One repository failing or hitting the rate limit is
reported and the rest carry on.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
repokeeper github status [--owner <name>] [--all] [--json] [--forks] [--exit-code]reports whatneeds attention across every non-archived repository of a GitHub user or organization (forks only
with
--forks). It runs from any folder and writes nothing.Per repository:
offwhen GitHub answers 403 "disabled"dynamicruns(Dependabot updates, Pages), pull request runs and cancelled/skipped runs are ignored;
nonewhen nothing ran; failures are listed with date and link
feat/fix/perf/revert/breaking; only those count as attention;
no tagsotherwisepackage-lock.json,npm-shrinkwrap.json,pnpm-lock.yaml(v5 to v9, pnpm 11's two documents)and
packages.configon the default branch; flags a package the graph names at a version nolockfile contains while a lockfile has it at another one. The output says that a commit touching
the manifest makes GitHub re-read it.
Default output: a table of the repositories that need attention, the details behind it, and
"N of M repositories clean".
--alllists every repository,--jsonprints everything,--exit-codeexits 1 when something needs attention (for a scheduled workflow). Four repositoriesare read at a time; a failing repository or the rate limit is reported under "could not check" and
the run carries on. Dependabot alerts follow the
Linkheader (cursor pagination), so the RESTclient now passes that header on.
Tests
12 new tests with the fake API (536 in total); typecheck, biome and build pass.
Real run
Limits
yarn.lockand csprojPackageReferenceare not readGITHUB_TOKENcannot readother repositories' Dependabot alerts