-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
checkout-multiple-repos-side-by-side doc example #1021
Comments
* wrap pipeline commands for submoduleForeach in quotes * Update src/git-auth-helper.ts drop extraneous space. Co-authored-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * Followed CONTRIBUTING.md instructions, updating dist/index.js * fixed package-lock.json * updating the pipeline so it runs from sh Co-authored-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Hey @maxatka, thank you for the feedback! The To directly answer your question We note in a few places that we use I've added in a PR to add a reference to the private section just to make it more clear :) |
@vanZeben Thanks for your feedback! |
The README.md contains example for mulitple checkouts in the context of one organization, if I'm not wrong.
May be, it's about to checkout public repository.
There is another example - checkout-multiple-repos-private, but is a repository of the same organization on GitHub for which the GitHub action is run, is considered "private" as well?
I thought if I run the action in private repository for my organization, other private repositories are accessible.
If not, it's better to precise the documentation by adding to "Checkout multiple repos (private)" something like:
...so if your want to checkout a different repository that is private (no matter if it's the same organization on GitHub or not)...
and to "Checkout multiple repos (side by side)" example to add something like:
Attention! You second repository must be public, even if it's from the same organization on GitHub that the action repository.
The text was updated successfully, but these errors were encountered: