jprdonnelly/docs
1
0
Fork 0
mirror of synced 2025-12-19 18:10:59 -05:00
Code Issues Projects Releases Wiki Activity

Add link to merge queue doc (#30983)

Browse Source
This commit is contained in:
Kevin Heis
2022-09-21 07:02:43 -07:00
committed by GitHub
parent 36248fefbb
commit 3330685feb
1 changed files with 5 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
contributing/deployments.md
View File

@@ -2,17 +2,19 @@
Staging and production deployments are automated by a deployer service created and maintained by @github/docs-engineering. Staging and production deployments are automated by a deployer service created and maintained by @github/docs-engineering.
### Staging deployments ### Preview deployments
When a pull request is **opened**, **reopened**, or **synchronized** (i.e has new commits), it is automatically deployed to a unique staging URL. When a pull request is **opened**, **reopened**, or **synchronized** (i.e has new commits), it is automatically deployed to a unique preview URL.
If a staging deployment fails, you can trigger a new deployment in a few ways: If a preview deployment fails, you can trigger a new deployment in a few ways:
- close and re-open the pull request - close and re-open the pull request
- push another commit to the branch - push another commit to the branch
- click **Update Branch** on the pull request page on github.com, if it's clickable - click **Update Branch** on the pull request page on github.com, if it's clickable
### Production deployments ### Production deployments
Docs uses [merge queue](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request-with-a-merge-queue).
When a pull request is merged to the repo's default branch, it is automatically deployed to production and the status is displayed on the PR's page on github.com. It can take up to 24 hours for changes to be visible on the site. When a pull request is merged to the repo's default branch, it is automatically deployed to production and the status is displayed on the PR's page on github.com. It can take up to 24 hours for changes to be visible on the site.
After a PR is closed, the branch is automatically deleted. This does not affect the deployment process. After a PR is closed, the branch is automatically deleted. This does not affect the deployment process.