Skip to content

Repo sync #46829

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.

Sign up for GitHub

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

Merged
docs-bot merged 2 commits into from
Nov 3, 2026
Merged

Repo sync #46829

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
63ebe9f
Clarify submitting fixes alongside contributors’ own issues (#64540)
subatoi Nov 3, 2026
ad9580d
docs: update gh-stack content from source docs (#63687)
docs-bot Nov 3, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 7 additions & 5 deletions .../contributing/collaborating-on-github-docs/about-contributing-to-github-docs.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,21 +17,23 @@ The documentation repository is the place to discuss and collaborate on the docu
## Issues

> [!NOTE]
> For larger updates, we highly recommend that you open an issue first, to give us the opportunity to review your proposal before you go ahead and raise a pull request.
> For larger updates, we highly recommend that you open an issue to give us the opportunity to review your proposal.

[Issues](/issues/tracking-your-work-with-issues/learning-about-issues/about-issues) are used to track tasks that contributors can help with. If an issue has a `triage` label, we haven't reviewed it yet, and you shouldn't begin work on it.
[Issues](/issues/tracking-your-work-with-issues/learning-about-issues/about-issues) are used to track tasks that contributors can help with. If an issue has a `triage` label, we haven't reviewed it yet. Don't begin work on another contributor's issue while it has this label.

If you've found something in the documentation content, or something about the docs.github.com website, that should be updated, search the open issues to see if someone else has reported the same thing. If it's something new, open an issue using a [template](https://github.com/github/docs/issues/new/choose). We'll use the issue to have a conversation about the problem you'd like to be fixed.<!-- markdownlint-disable-line search-replace -->

### Submitting a fix for your own issue

If you open an issue and want to contribute the fix yourself, open a pull request with your proposed fix at the same time. Link the pull request to your issue, and don't wait for us to approve the issue. We'll still need to review and approve the issue before we can accept the contribution.

### Working on other contributors' issues

> [!NOTE]
> We will close any pull requests raised against existing issues without a `help wanted` label.
> We will close any pull requests raised against other contributors' issues without a `help wanted` label.

To make sure all of our contributors have the best experience, please don't raise any pull requests against an existing issue that another user has raised until it's been marked with a `help wanted` label. We need to properly assess all issues before we can accept community contributions, and determine whether it's something we need to fix internally, or how many articles are affected and what the scope of the fix will be.

You can still raise a pull request and an issue at the same time, if you're confident about the nature of your contribution.

## Pull requests

A [pull request](/pull-requests/reference/pull-requests) is a way to suggest changes in our repository. When we merge those changes, they're deployed to the live site within 24 hours.
Expand Down
Loading
Loading