Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Fix typo in co-author example #24817

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 2 commits into from
Apr 4, 2023
Merged

Fix typo in co-author example #24817

merged 2 commits into from
Apr 4, 2023

Conversation

subeom7
Copy link
Contributor

@subeom7 subeom7 commented Apr 1, 2023

This commit fixes a typo in the co-author example in the creating-a-commit-with-multiple-authors.md documentation. The original line was:

Co-authored-by: AUTHOR-NAME [email protected]

The corrected line is:

Co-authored-by: ANOTHER-NAME [email protected]

This change ensures that both examples follow the same format and maintain consistency to avoid confusion.

Why:

This commit fixes a typo in the co-author example of creating-a-commit-with-multiple-authors.md documentation. The change ensures that both examples follow the same format and maintain consistency to avoid confusion.

Closes:

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

The original line was: Co-authored-by: AUTHOR-NAME [email protected]

The modified line is: Co-authored-by: ANOTHER-NAME [email protected]

Check off the following:

  • I have reviewed my changes in staging (look for the "Automatically generated comment" and click the links in the "Preview" column to view your latest changes).
  • For content changes, I have completed the self-review checklist.

@subeom7
Fix typo in co-author example
091ea34 
This commit fixes a typo in the co-author example in the GitHub documentation. The original line was:

Co-authored-by: AUTHOR-NAME <[email protected]>

The corrected line is:

Co-authored-by: ANOTHER-NAME <[email protected]>

This change ensures that both examples follow the same format and maintain consistency to avoid confusion.
@welcome
Copy link

welcome bot commented Apr 1, 2023

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 Apr 1, 2023
@github-actions
Copy link
Contributor

github-actions bot commented Apr 1, 2023 •
edited
Loading

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/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors.md fpt
ghec
ghes@ 3.8 3.7 3.6 3.5 3.4
ghae
 fpt
ghec
ghes@ 3.8 3.7 3.6 3.5 3.4
ghae

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

@cmwilson21
Copy link
Contributor

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

@cmwilson21 cmwilson21 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 pull requests Content related to pull requests and removed triage Do not begin working on this issue until triaged by the team labels Apr 3, 2023
skedwards88
skedwards88 approved these changes Apr 4, 2023
View reviewed changes
Copy link
Contributor

@skedwards88 skedwards88 left a comment

Choose a reason for hiding this comment

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

Thanks for this fix! We'll get this merged down for you.

@skedwards88 skedwards88 added the ready to merge This pull request is ready to merge label Apr 4, 2023
@cmwilson21 cmwilson21 enabled auto-merge April 4, 2023 14:55
@cmwilson21 cmwilson21 added this pull request to the merge queue Apr 4, 2023
Merged via the queue into github:main with commit ec9d28c Apr 4, 2023
@github-actions
Copy link
Contributor

github-actions bot commented Apr 4, 2023

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
Reviewers
1 more reviewer

@skedwards88 skedwards88 skedwards88 approved these changes

Reviewers whose approvals may not affect merge requirements
Assignees
No one assigned
Labels
content This issue or pull request belongs to the Docs Content team pull requests Content related to pull requests ready to merge This pull request is ready to merge waiting for review Issue/PR is waiting for a writer's review
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@subeom7 @cmwilson21 @skedwards88