Repository navigation
docs: fix wording faults in the repo standards and settle five rules - #25
Merged
Merged
Conversation
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 changed
Wording faults, no rule change:
if:rule now excepts theautomergeanddeploy-mergedjobs, which the Dependabot section prescribes with a job-levelif:.Rules settled by the owner:
${{ vars.RUNNER || 'ubuntu-latest' }}for the self-hosted runner..oxlintrc.jsondenies warnings withoptions.denyWarnings: true, named exactly so it can be checked.@types/nodemajor updates; it moves with.nvmrc, by hand.docs/changelog.mdbe that home.Why
An audit of 28 repositories against the standard found one rule the standard's own prescribed jobs break, two rules stated twice, private repository names in this public file, and places where the text and the repositories disagreed with no shown harm. Two independent reviews argued against each proposed rule change; these five are what survived. Left as written, with the differing repositories recorded instead: site names, the commit-type table, seconds per step, and
uv.lockfor Python.No issue: docs
How you checked it
scripts/check: 0Every relative link in
docs/repo-standards.mdresolves, including the new#dependabotanchor.options.denyWarningsexists since oxlint 1.52.0; with it a lint warning exits 1, as with--deny-warnings(tested on 1.88).Dependabot runs in the private repositories do land on the self-hosted runner.
A bug fix comes with a test that fails without it
Docs match how it works now
No secrets or private information