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

Update getting-started.md - branch v0.14.0 does not exist #1768

Closed

Conversation

fcbry
Copy link

@fcbry fcbry commented Jul 23, 2024

Update getting-started.md - branch v0.14.0 does not exist

@fcbry fcbry requested a review from a team as a code owner July 23, 2024 17:35
@fcbry fcbry force-pushed the fix/remove-doc-refs-to-non-existing-branch branch from d636fb0 to 1b2c48f Compare July 23, 2024 17:37
@Stratus3D
Copy link
Member

Hi @fcbry, the instructions are correct, at least for recent versions of Git.

-b
--branch

Instead of pointing the newly created HEAD to the branch pointed to by the cloned repository’s HEAD, point to branch instead. In a non-bare repository, this is the branch that will be checked out. --branch can also take tags and detaches the HEAD at that commit in the resulting repository.

-- from https://git-scm.com/docs/git-clone

The Git flag is poorly named, but we instruct the user to pass in the tag via the --branch option, which is valid.

@Stratus3D Stratus3D closed this Jul 23, 2024
@fcbry
Copy link
Author

fcbry commented Sep 2, 2024

@Stratus3D - I mean the branch doesn't exist, and there is a different branch referenced in the japanese docs

@Stratus3D
Copy link
Member

@fcbry it's not a branch it's a tag.

@fcbry
Copy link
Author

fcbry commented Sep 5, 2024

My appologies, I skimmed your response and failed to pick up on the rather obvious and correct point:

The Git flag is poorly named, but we instruct the user to pass in the tag via the --branch option, which is valid.

😊

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