Skip to content

Auto merge doc fix #32304

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 5 commits into from
Apr 1, 2024
Merged

Auto merge doc fix #32304

merged 5 commits into from
Apr 1, 2024

Conversation

ktauchathuranga
Copy link
Contributor

Why: its because I was searching for how to enable auto-merge in my repo, I found the documentation but it was unclear and I search trough settings like 15 min before I found it

Closes: #32303

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

I added a screenshot of the location of the option and cleared out the exact path in the text section.

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.

Copy link

welcome bot commented Mar 30, 2024

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.

@github-actions github-actions bot added the triage Do not begin working on this issue until triaged by the team label Mar 30, 2024
Copy link
Contributor

github-actions bot commented Mar 30, 2024

Automatically generated comment ℹ️

This comment is automatically generated and will be overwritten every time changes are committed to this branch.

The table contains an overview of files in the content directory that have been changed in this pull request. It's provided to make it easy to review your changes on the staging site. Please note that changes to the data directory will not show up in this table.


Content directory changes

You may find it useful to copy this table into the pull request summary. There you can edit it to share links to important articles or changes and to give a high-level overview of how the changes in your pull request support the overall goals of the pull request.

Source Preview Production What Changed
repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository.md fpt
ghec
ghes@ 3.12 3.11 3.10 3.9
fpt
ghec
ghes@ 3.12 3.11 3.10 3.9

fpt: Free, Pro, Team
ghec: GitHub Enterprise Cloud
ghes: GitHub Enterprise Server

@nguyenalex836 nguyenalex836 added content This issue or pull request belongs to the Docs Content team waiting for review Issue/PR is waiting for a writer's review repositories Content related to repositories and removed triage Do not begin working on this issue until triaged by the team labels Apr 1, 2024
@nguyenalex836
Copy link
Contributor

@ktauchathuranga Thanks so much for opening a PR! I'll get this triaged for review ✨

nguyenalex836
nguyenalex836 previously approved these changes Apr 1, 2024
@nguyenalex836
Copy link
Contributor

@ktauchathuranga Thanks so much for opening a PR with this update! I made a few minor edits to make this update more closely align with our style guide 💛 I'll update the branch and get this merged once tests are passing 🍏

@nguyenalex836 nguyenalex836 enabled auto-merge April 1, 2024 22:37
@nguyenalex836 nguyenalex836 removed the waiting for review Issue/PR is waiting for a writer's review label Apr 1, 2024
@nguyenalex836 nguyenalex836 added this pull request to the merge queue Apr 1, 2024
Merged via the queue into github:main with commit fa1f4c1 Apr 1, 2024
Copy link
Contributor

github-actions bot commented Apr 1, 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

@ktauchathuranga
Copy link
Contributor Author

@ktauchathuranga Thanks so much for opening a PR with this update! I made a few minor edits to make this update more closely align with our style guide 💛 I'll update the branch and get this merged once tests are passing 🍏

yeaah.... i am sorry for the oversight. but you fixed it. thank you... 😇

@nguyenalex836
Copy link
Contributor

It was no problem at all - thank you for your contribution! 💛 ✨

If you're up for tackling another issue, take a look at our help wanted section to find open issues you can work on 😄

@ktauchathuranga ktauchathuranga deleted the auto-merge-doc-fix branch April 2, 2024 15:11
@ktauchathuranga ktauchathuranga restored the auto-merge-doc-fix branch April 2, 2024 15:11
@ktauchathuranga ktauchathuranga deleted the auto-merge-doc-fix branch April 2, 2024 15:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content This issue or pull request belongs to the Docs Content team repositories Content related to repositories
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Unclear about auto merge option location
2 participants