Skip to content

Update merge-queue gated feature for GHES 3.12 #31946

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

Merged
merged 6 commits into from
Mar 5, 2024

Conversation

willsmythe
Copy link
Contributor

@willsmythe willsmythe commented Mar 5, 2024

Why:

The "Who can use this feature" section for Merge Queue related docs (when viewing GHES 3.12) is confusing since it currently only mentions Enterprise Cloud. For example:

https://docs.github.com/en/[email protected]/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-a-merge-queue

This change updates the gated feature details to be correct for GHES.

Note: the MQ feature is currently gated to GHES 3.12 and later.

What's being changed (if available, include any code snippets, screenshots, or gifs):

Fixes the "Who can use this feature" section on Merge Queue related pages when viewing GHES 3.12 and later docs.

Check off the following:

  • I have reviewed my changes in staging, available via the View deployment link in this PR's timeline (this link will be available after opening the PR).

    • For content changes, you will also see an automatically generated comment with links directly to pages you've modified. The comment won't appear if your PR only edits files in the data directory.
  • For content changes, I have completed the self-review checklist.

The "who can use this feature" section for Merge Queue related docs (when viewing GHES 3.12) is confusing since it currently only mentions Enterprise Cloud. This updates that to indicate MQ is available on all org-owned repos in GHES.

Note: the MQ feature is currently gated to GHES 3.12 and later.
@github-actions github-actions bot added the triage Do not begin working on this issue until triaged by the team label Mar 5, 2024
@willsmythe
Copy link
Contributor Author

willsmythe commented Mar 5, 2024

Copy link
Contributor

@isaacmbrown isaacmbrown left a comment

Choose a reason for hiding this comment

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

Looks good, thanks @willsmythe 🙇

@isaacmbrown isaacmbrown added this pull request to the merge queue Mar 5, 2024
Merged via the queue into github:main with commit d610c00 Mar 5, 2024
Copy link
Contributor

github-actions bot commented Mar 5, 2024

Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours. If you're looking for your next contribution, check out our help wanted issues

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage Do not begin working on this issue until triaged by the team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants