-
Notifications
You must be signed in to change notification settings - Fork 59
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
Using multi-repo manifests without address for review #9
Comments
This is fixed in pull request #12.
This is because for single repository, there is no manifest file for it, and there maybe more remotes defined in .git/config. So it's necessary to add "--remote" support for single repository.
For multiple repositories, we can define different remote in See pull request #11. |
I will add test cases tomorrow. |
Thank you, it sounds perfect. I'm still working on a system with the review protocol, so close when you think it is ready. |
Can this review protocol you mentioned work with git-repo? Would you like to add the name of your platform to "git-repo ready" list in a section of the |
Just trying to implement AGitFlow so yes, once I've got it working i'll send a PR for the |
When dealing with e.g. manifest repositories e.g. here on github, where there is no address for review in the manifest,
you currently get
ERROR: bad address for review ''
. Its a bit difficult to add try and add remotes to the repo downloaded repositories fromgit repo sync
.It would be nice if there was a way to easily add remotes to all the repositories checked out,
It seems like perhaps if there was a
--remote-manifest-url
togit repo init
git repo upload --remote
, gives the impression that it only works with--single
repositories, (correct?)--remote string
use specific remote for upload (use with --single)
Is there a nice way to make
--remote
work with multiple repositories, and if not do you think adding something such as--remote-manifest-url
would be a good way to do so?The text was updated successfully, but these errors were encountered: