Repository navigation
v0.3.0: rate-limit fallback, --fix --dry-run, corpus scripts
What's new
- Rate-limit fallback (#5): at the REST API limit,
action.ymlfiles are read fromraw.githubusercontent.comand tags are listed withgit ls-remote(public repositories; your token is never passed to git). The summary and one stderr line say how many lookups used it;--no-fallbackrestores the hard stop. --fix --dry-run(#7, first half): prints a unified diff thatgit applyaccepts (LF and CRLF files) and writes nothing.--pin-onlyis still open.- Corpus scripts (#8):
scripts/corpus/fetch.pyandcompare.pyreproduce the precision measurement. Re-run on the same 240 repositories: 1264/1277 distinct references agree with the independent checker (99.0 %), 13 disagreements (hand-check of that run not repeated this time).
Verified vs not
- Fallback verified against the real raw.githubusercontent.com and
git ls-remoteusing an API stub that always answers 403/rate-limited; unit tests use local look-alike servers and realgit ls-remoteoutput. - The agreement figure compares two implementations by the same author; it is not GitHub-runtime ground truth.
- Marketplace:
action.ymlhas the metadata; publishing is a manual step for the repository owner.
Full list: CHANGELOG.md