Skip to content

Fix the command of deleting a remote branch #25053

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 1 commit into from
Apr 17, 2023
Merged

Fix the command of deleting a remote branch #25053

merged 1 commit into from
Apr 17, 2023

Conversation

fei6409
Copy link
Contributor

@fei6409 fei6409 commented Apr 17, 2023 •
edited
Loading

Why:

Closes: #25052

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

In https://docs.github.com/en/get-started/using-git/pushing-commits-to-a-remote-repository#deleting-a-remote-branch-or-tag, a missing whitespace is restored in the command.

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.

@welcome
Copy link

welcome bot commented Apr 17, 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 17, 2023
@github-actions
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
get-started/using-git/pushing-commits-to-a-remote-repository.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

steveward
steveward approved these changes Apr 17, 2023
View reviewed changes
Copy link
Member

@steveward steveward left a comment

Choose a reason for hiding this comment

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

Good catch @fei6409, I'll get this merged!

@steveward steveward added content This issue or pull request belongs to the Docs Content team using git Content related to using git and removed triage Do not begin working on this issue until triaged by the team labels Apr 17, 2023
@steveward steveward enabled auto-merge April 17, 2023 19:14
@steveward steveward added this pull request to the merge queue Apr 17, 2023
Merged via the queue into github:main with commit e2d847f Apr 17, 2023
@github-actions
Copy link
Contributor

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 ⚡

@fei6409 fei6409 deleted the fix-doc branch April 18, 2023 04:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@steveward steveward steveward approved these changes

Assignees
No one assigned
Labels
content This issue or pull request belongs to the Docs Content team using git Content related to using git
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Command typo in get-started/using-git/pushing-commits-to-a-remote-repository
2 participants
@fei6409 @steveward