[maintainer edit for spammy content]

[Taykong]

Code of Conduct

• I have read and agree to the GitHub Docs project's Code of Conduct

Pre-requisites

• My application to the GitHub Technology Partner Program is approved.

Tasks

• MUST follow our general contributing guidelines for voice and markup format.
• MUST emphasize how the third-party product works with GitHub.
• MUST be written in Markdown format, using one of the templates provided.
• MUST include the name and URL of the GitHub technology partner responsible for maintenance of the documentation being contributed. This should be added via the contributor.name and contributor.URL properties in the template's YAML frontmatter.
• MUST be proposed via a pull request to this repo following the GitHub Flow.
• MUST be located in the root of the content folder. Your filename MUST match the GitHub technology partner name, and use the .md file extension.

Pull Request

• MUST reference this issue, e.g. via closes [this issue number].
• MUST pass the automated CI checks.
• MUST include links to supporting material demonstrating the functionality being documented (this can be a link to a public GitHub repo, or a video / screencast walkthrough).

Tasks

Preview Give feedback

1. docs: Remove periods from Managing deploy keys list #34540
   authentication content ready to merge +3
2. content/repositories/archiving-a-github-repository/index.md #34541
   invalid +1
3. Remove periods from list in about-mandatory-two-factor-authentication#about-eligibility-for-mandatory-2fa #34521
   authentication content good first issue +3
4. Bump peter-evans/create-pull-request from 6.1.0 to 7.0.0 #34486
   dependencies github_actions triage +3
5. 🌹 #34539
   invalid +1
6. update in authentication to follow the content style guide #34537
   authentication content +2
7. Remove periods from list in managing-deploy-keys#pros-of-installation-access-tokens #34522
   authentication content good first issue +3
8. Updated about-mandatory-two-factor-authentication.md #34524
   authentication content ready to merge +3
9. Wrong sub-title in the French version of authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent #34531
   authentication content localization +3
10. Replace misleading documentation about action inputs and outputs #33916
    SME reviewed actions content +3
11. Mini-TOC shows inline instead of on the side #34529
    actions content +2
12. Correct text to match URL ID example in project automation documentation #34528
    content issues ready to merge +3
13. "Actions Runner Controller" articles expand wrong tree item #34526
    actions content needs SME waiting for review +4
14. Correct text to match URL ID example in project automation documentation #34527
    content issues +2
15. [Improvement]: Audit all {%- versioning to check whether GHEC versioning is correct #15731
    MLH fellowship content +2
16. Use consistent language for placeholders in AWS OpenID setup #34525
    actions content ready to merge +3
17. Initial commit #34538
    invalid +1

[docs-bot]

This issue may have been opened accidentally. I'm going to close it now, but feel free to open a new issue with a more descriptive title!