-
Notifications
You must be signed in to change notification settings - Fork 60.6k
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
Clarify inactive status made to same environment name #2430
Conversation
Previous deployments to the same environment (name) will automatically be marked inactive so this update makes that clearer. Previously, the doc said all deployments in the same respository. Ref: https://developer.github.com/changes/2016-04-06-deployment-and-deployment-status-enhancements/#automatic-creation-of-inactive-statuses
Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines. |
Thanks so much for opening a PR! I'll get this triaged for review ✨ |
This PR is stale because it has been open 7 days with no activity and will be automatically closed in 3 days. To keep this PR open, update the PR by adding a comment or pushing a commit. |
@janiceilene - Do I need to do anything here to prevent this PR from getting closed? |
Nothing you need to do @bradymholt 💛 Thanks for your patience! Our small team is working our way through reviewing all of the amazing contributions ✨ |
This PR is stale because it has been open 7 days with no activity and will be automatically closed in 3 days. To keep this PR open, update the PR by adding a comment or pushing a commit. |
This PR is stale because it has been open 7 days with no activity and will be automatically closed in 3 days. To keep this PR open, update the PR by adding a comment or pushing a commit. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚀 Thank you for adding this clarification! I made one small optional wording suggestion. Let me know what you think, then I'll get this merged down for you.
Co-authored-by: Sarah Edwards <skedwards88@github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚀 LGTM! I'll get this merged down for you.
Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours. |
Previous deployments to the same
environment
name will automatically be marked inactive so this update makes that clearer. Previously, the docs said all deployments in the same repository would be marked inactive.Ref: https://developer.github.com/changes/2016-04-06-deployment-and-deployment-status-enhancements/#automatic-creation-of-inactive-statuses
Why:
Per #2429, the previous documentation needed clarification.
What's being changed:
The Inactive deployments section of the REST Reference docs.
Check off the following:
Fixes #2429