Skip to content

Fixing the error about new branch #26307

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

Closed
wants to merge 1 commit into from

Conversation

Harshil-Jani
Copy link
Contributor

This will help new commers to better execute this operation and make them less worried in case they are new to git environment.

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

A line into the guides about the checkout of new pull requests locally. After fetching the changes, You need to create a new branch and the code snippet is not for the new branch which may confuse new users.

Check off the following:

  • I have reviewed my changes in staging, available via the View deployment link in this PR's timeline.

    • 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.

This will help new commers to better execute this operation and make them less worried in case they are new to git environment.
@welcome
Copy link

welcome bot commented Jun 28, 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 Jun 28, 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
pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally.md fpt
ghec
ghes@ 3.9 3.8 3.7 3.6 3.5
ghae
fpt
ghec
ghes@ 3.9 3.8 3.7 3.6 3.5
ghae

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

@Harshil-Jani
Copy link
Contributor Author

Sorry, I have overlooked this and understood HEAD:branch-name as branch name of the PR raiser. But if at that point we are giving our specified branch name then we don't need a new branch. Henceforth, I am closing the PR.

@cmwilson21
Copy link
Contributor

@Harshil-Jani Thanks for submitting the PR and coming back and updating/closing it! ✨

Please take a look at our help wanted section to find open issues you can work on.

Thank you for your interest in improving GitHub Docs! 💖

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

Successfully merging this pull request may close these issues.

2 participants