Skip to content
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

automatically-merging-a-pull-request.md #35892

Closed
wants to merge 1 commit into from
Closed

Conversation

Knoph1
Copy link

@Knoph1 Knoph1 commented Jan 10, 2025

Update automatically-merging-a-pull-request.md

Why:

Closes:

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

Check off the following:

  • A subject matter expert (SME) has reviewed the technical accuracy of the content in this PR. In most cases, the author can be the SME. Open source contributions may require a SME review from GitHub staff.
  • The changes in this PR meet the docs fundamentals that are required for all content.
  • All CI checks are passing.

Update automatically-merging-a-pull-request.md
Copy link

welcome bot commented Jan 10, 2025

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 Jan 10, 2025
@Knoph1
Copy link
Author

Knoph1 commented Jan 10, 2025

Update automatically-merging-a-pull-request.md

Copy link
Contributor

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
pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request.md fpt
ghec
ghes@ 3.15 3.14 3.13 3.12 3.11 3.10
fpt
ghec
ghes@ 3.15 3.14 3.13 3.12 3.11 3.10

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

@subatoi
Copy link
Contributor

subatoi commented Jan 10, 2025

Hi, I'm afraid we won't be accepting this change—please see https://docs.github.com/en/contributing/style-guide-and-content-model/style-guide#product-names for further information

Thanks for your interest in the GitHub Docs: please feel free to take a look at our issues marked help wanted

@subatoi subatoi closed this Jan 10, 2025
@Knoph1
Copy link
Author

Knoph1 commented Jan 10, 2025

Hi there,
I'm quite interested majorly in Back-end development & Technical Writing while also minoring in grammar checkups and spellings.
Hope it'll be helpful to.

@Knoph1
Copy link
Author

Knoph1 commented Jan 10, 2025

Hi, I'm afraid we won't be accepting this change—please see https://docs.github.com/en/contributing/style-guide-and-content-model/style-guide#product-names for further information

Thanks for your interest in the GitHub Docs: please feel free to take a look at our issues marked help wanted

Thanks for the quick reply, Sir.

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