Recently I updated a collect file to fetch from a specified branch instead of the default branch.
"mojo collect" still finished successfully but the repo remained on the original branch.
I would expect in this case for codetree to complain about the change in source, much as it does when the source itself is changed, and to require overwrite=True to proceed.
Recently I updated a collect file to fetch from a specified branch instead of the default branch.
"mojo collect" still finished successfully but the repo remained on the original branch.
I would expect in this case for codetree to complain about the change in source, much as it does when the source itself is changed, and to require overwrite=True to proceed.
$ cat $MOJO_SPEC/ $MOJO_STAGE/ ../collect /git.launchpad. net/charm- k8s-mattermost; branch= built origin/ master 7568a21349d56c6 1e15892d49 mojo-prod- mattermost/ xenial/ production/ build/mattermos t branch mojo-prod- mattermost/ xenial/ production/ build/mattermos t mojo-prod- mattermost/ xenial/ production/ charms/ xenial/ mattermost /git.launchpad. net/charm- k8s-mattermost b0f0e2b8a5db911 786ebb2a91 mojo-prod- mattermost/ xenial/ production/ build/mattermos t branch
mattermost git+https:/
$ mojo collect
[...]
2020-08-18 22:25:21 [INFO] Updating repository at mattermost from refs/remotes/
2020-08-18 22:25:21 [INFO] Repository mattermost at revision 2b68f795ca39293
[...]
$ git -C /srv/mojo/
* master
$ rm -rf /srv/mojo/
$ rm -rf /srv/mojo/
$ mojo collect
[...]
2020-08-18 22:35:14 [INFO] Cloning repository at mattermost from https:/
2020-08-18 22:35:15 [INFO] Repository mattermost at revision b261ac7a54e390b
[...]
$ git -C /srv/mojo/
* built
$ _