Repository navigation
docs: add conventional status badges to the READMEs - #55
Merged
Merged
Conversation
Contributor
Author
Coverage
|
Contributor
Author
|
Loop pr-review — approve ✅ Independent check of the diff (
Gates re-run from this checkout: No L1/L2 problems. Awaiting the owner's approving review and merge. |
This was referenced Sep 17, 2026
Alex1990
pushed a commit
that referenced
this pull request
Sep 17, 2026
agentEnv() injected 'tiny-oss loop <loop@users.noreply.github.com>' as the git identity under auto. That address belongs to the real, unrelated GitHub user @loop (id 1519971), so every loop commit - 8ec1b1e (PR #50) and 4d2735a/35c7312 (PR #55) - was falsely attributed to a stranger (#52, #56). Use GitHub Actions' own bot instead, the same identity the host's PR is authored by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>. A bot noreply address is not a user account, so it cannot be squatted. Only future commits change; the historical ones stay as they are.
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.
Closes #54
loop-task: #54
Why
Issue #54 asks for the common README badges. Today
README.mdcarries only the npm-version badge andREADME_zh-CN.mdhas none.What
One badge row directly under the
# tiny-ossheading in bothREADME.mdandREADME_zh-CN.md(parity), keeping the existing npm-version badge and adding the conventional set:npm/vnpm/dmnpm/lLICENSEonmainci.ymlbundlephobia/minzipnode/vDocs-only: no source, dependency or workflow file change; commit type
docsper AGENTS.md.Verification
npm/v,npm/dm,npm/l,bundlephobia/minzip,node/v, theci.ymlActions badge;LICENSE, Actions page, Bundlephobia page).pnpm lint— 0 errors (39 pre-existing warnings).pnpm fmt:check— all files formatted.pnpm buildthenpnpm check:types— exit 0 (check:typesreads the generateddist/types).pnpm test:azure-oracle— all checks passed.pnpm exec vitest run --browser.headlesswithpnpm serve— 22 files passed, 231 passed / 26 skipped (integration specs skip without credentials).Review
Two-lens review (correctness/regression and standards/safety) found no L1/L2 problems; the independent
pr-reviewstage re-checks the diff.