Skip to content

Conversation

ByteKatana
Copy link
Contributor

  • The page(s) are in the correct platform directories: common, linux, osx, windows, sunos, android, etc.
  • The page(s) have at most 8 examples.
  • The page description(s) have links to documentation or a homepage.
  • The page(s) follow the content guidelines.
  • The page(s) follow the style guide.
  • The PR title conforms to the recommended templates.
  • Version of the command being documented (if known):

@ByteKatana ByteKatana requested a review from tansiret as a code owner October 2, 2025 06:22
@github-actions github-actions bot added the new translation PRs translating a page(s) from English to other languages. label Oct 2, 2025
Copy link
Member

@kbdharun kbdharun left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks for your contribution.

@Managor
Copy link
Member

Managor commented Oct 8, 2025

Please don't merge main when it's not needed. It creates unnecessary email spam.

@ByteKatana
Copy link
Contributor Author

Hi, sorry for causing email spam. I just wanted to make it ready for merge since it had received two approvals. I’ll definitely be careful about that in the future.

@Managor
Copy link
Member

Managor commented Oct 8, 2025

We're currently waiting @tansiret to review this since he's a codeowner. If he doesn't, we'll merge this automatically when the PR is two weeks old

If a PR is not ready for a merge, the same spot that says to "Update branch" will instead say that there's a merge conflict. In that case you do need to act.

@Managor Managor merged commit e50a50c into tldr-pages:main Oct 13, 2025
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

new translation PRs translating a page(s) from English to other languages.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants