We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Re the steps in CLOSED_CONTRIBUTIONS.md
git checkout internal/main
error: pathspec 'internal/main' did not match any file(s) known to git
Note: while this is effectively an "internal" issue, we are trying to be as open as possible with our work for this open source repository.
The text was updated successfully, but these errors were encountered:
Could you try git fetch --all, then attempt to check out again?
git fetch --all
I thought fetch also grabbed remotes, but after testing it that doesn't seem to be the case
➜ git fetch remote: Enumerating objects: 21, done. remote: Counting objects: 100% (21/21), done. remote: Compressing objects: 100% (19/19), done. remote: Total 21 (delta 3), reused 4 (delta 2), pack-reused 0 (from 0) Unpacking objects: 100% (21/21), 55.66 KiB | 1017.00 KiB/s, done. From github.com:nginx/documentation 26173a28..b2dd73f8 main -> origin/main + c3c256cf...94aaf175 mjang-patch-2 -> origin/mjang-patch-2 (forced update)
➜ git fetch --all Fetching origin Fetching internal remote: Enumerating objects: 106, done. remote: Counting objects: 100% (79/79), done. remote: Compressing objects: 100% (32/32), done. remote: Total 106 (delta 61), reused 52 (delta 47), pack-reused 27 (from 2) Receiving objects: 100% (106/106), 23.37 KiB | 7.79 MiB/s, done. Resolving deltas: 100% (70/70), completed with 14 local objects. From github.com:nginx/internal-docs ...
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
Describe the bug
Re the steps in CLOSED_CONTRIBUTIONS.md
git checkout internal/main
and I get the following error:Expected behavior
Your environment
Note: while this is effectively an "internal" issue, we are trying to be as open as possible with our work for this open source repository.
The text was updated successfully, but these errors were encountered: