-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tracker issue: 2023 #11146
Comments
For the French style-guide; only I have found it is common case to add an extra space for the next characters, not only the colon:
|
Yep, that seems to be the case. While creating a PR we can mention it too. |
Regarding the contributing guide: we could mention that one can run the linter locally. Imo this would then close #4986. |
Agreed, I have some free time tomorrow, will work on this. |
Documenting Progress
This checklist was moved from #10755 (as suggested by @sebastiaanspeck).
Section 1: Main repo and Org
To update
Note
To avoid merge conflicts, if there is an open PR updating the style guide, it is recommended to wait for it to get merged before creating a new one.
Style guide
Display help
andDisplay version
generic term preference and order. [Existing informal rule] → style-guide: add help and version commands section #11854|
[Existing informal rule] (Already present, the wording was improved)--opt arg
, improve wording #10906common
, update description; style-guide: add description guidelines #10858stdout
over standard output [Existing informal rule] → style-guide: add guidelines for standard streams; fix remaining pages #11196common
, update description; style-guide: add description guidelines #10858QuotesBackticks (Ref. zforce: add page #10868) → krita: move tocommon
, update description; style-guide: add description guidelines #10858latest
or none) →style-guide: add and update documentation about URLs #11320Contributing guide
tldr-lint
before creating a PR → CONTRIBUTING: update page, fix Markdown syntax #11669Scripts directory
PR template
Add comment highlighting running tldr-lint locally or explaining the PR would go through tldr-bot running the same→ PULL_REQUEST_TEMPLATE: add testing page using tldr-lint to checklist #11671 (Proposal dropped)Client Specification
MAINTAINERS guide
Add "platform addition consideration section" to document notability criteria (i.e should have a stable release, etc) for adding a new platform→ Dropped this as we rarely add new platforms and the addition must be discussed with the maintainers in the chatroom then and there (and a general guideline would be too restrictive).Community roles
To create
Others
Platform Additions
Miscellaneous
main
as the default branch for all Repostlrc
andtldr-translation-pairs-gen
) → [Archive] Default branch inextldr
has been switched to main, branch protection has been enabled for main branch #10830, [Archive] Branch protection for main branch has been enabled fortldr-lint
#10831, [Archive] Updated default branch frommaster
->main
intldr-node-client
, added branch protection rule for the main branch #10832, [Archive] Branch protection for main branch has been enabled fortldr-c-client
#10833Run scripts and add standard (alias page) and more information link translation→ pages/*: add standard translation and links #11331Section 2: tlrc
tlrc
)tlrc
to Winget → Add package: tldr-pages.tlrc 1.6.0 microsoft/winget-pkgs#123733tlrc
to Homebrew → tlrc 1.7.1 (new formula) Homebrew/homebrew-core#152996tlrc
in Wikitlrc
in README →README: update Homebrew client to Rust clienttlrc
#11369The text was updated successfully, but these errors were encountered: