-
Notifications
You must be signed in to change notification settings - Fork 54
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
git-autoshare never triggered? #26
Comments
That needs investigation. Does not sound trivial at first glance. Note that we don't really suffer much about this in our workflow, because git-aggregate is infrequent, comparing to git cloning of frozen references (aka pip install requirements.txt :). git-aggregate is typically done at the beginning of a development cycle to refresh base versions of unmerged PRs. |
@sbidou. Yes it's also infrequent for us. Today it's just about remembering to do a git clone manually when starting a new Docky project. Eventually we do that in akretion/ak, I will check with the rest of the team and confirm if we can tackle it this way. |
This was resolved in #55 |
thanks, BTW both tools absolutely rock! |
just a message to confirm my tests show it was really fixed. Thanks again. |
Hello @sbidoul. I like both your git-aggregator and git-autoshare tools. However, git-aggregator triggers
git init
andgit fetch
but never thegit clone
command (see https://github.com/acsone/git-aggregator/blob/master/git_aggregator/repo.py ).So git-autoshare will never get triggered unless you do a git clone of the repo previously before calling git-aggregator.
Woudn't there be a way to trigger git clone/git-autoshare when the repo is empty at least?
What do you think?
The text was updated successfully, but these errors were encountered: