new push parameters: --tag / --tag-refresh

[oboukili]

Hello,

This PR introduces --tag and --tag-refresh parameters to the push command:

  The `--tag` option will apply a given (non-annotated) tag to the specified
  subrepos' upstream HEAD, provided that they were staged for changes, leaving
  the parent repository unchanged.

  The `--tag-refresh` will apply the given tag (with `--tag`) to all specified
  subrepos' upstream HEAD even if they were not staged for changes.

I had a need to push to multiple subrepos, passing on a common information. I thought a tag would be a good way to do it.

This should also resolve issue #188.

I also fixed some cleaning bugs with the delete-branch -> delete-worktree calls.
I've based of this PR on the release/0.4.0 branch.

Cheers,

[oboukili]

I would appreciate some help with the CI tests failing :) I don't know where to look at.

[oboukili]

@grimmySwe or @ingydotnet would you have some time to give me a hand?

[JacopKane]

This PR sounds great for pushing tags altogether, wish it could have a go

[oboukili]

Still no news, hard at work I presume?
Cheers

[oboukili]

Why was it closed?

[ingydotnet]

@oboukili hmm. Looks like my fault. Since 0.4.0 is now on master I deleted the release/0.4.0 branch, and that seems to have auto-closed this.

Can you see if it is possible to re-target master?

I wonder how many other PRs I closed by doing this.

@grimmySwe take note...

[ingydotnet]

I had a list of 12 open PRs before I unwittingly auto-closed them.
The auto-closed ones are:

• Move the .gitrepo config file to .gitrepo/config (version 0.4.1 for release/0.4.0 branch) #379
• Fixes Travis CI build. It was not checking out a branch. #358
• Report an error when the subrepo parent not found. #356
• new push parameters: --tag / --tag-refresh #337
• Add Prefix Option https://github.com/ingydotnet/git-subrepo/issues/319 #332
• Fix #313: Ensured "-u" options is respected by "subrepo:push()". #314
• Added (very) basic fish support #284

[ingydotnet]

I can try to repush the release/0.4.0 branch and see what happens to the 7 closed PRs.

[ingydotnet]

I re-pushed release/0.4.0 and clicked the 'Reopen pull request' button.

This PR still needs to re-target master I would think. @oboukili let me know if you figure out how to do that.

I'll reopen the others for now, and wait for more clarity.

[oboukili]

@ingydotnet alright I changed the PR's base branch to target master instead.

[admorgan]

Was this closed because you were tired of waiting or because you found a better solution? I am still working through the backlog and this seems like a great patch.

[oboukili]

Hello Indeed it has been more than a year, I was doing some old PR cleanup, I can reopen it if it is still of some interest.

[twpedersen]

This would be a great feature!

[admorgan]

The way I read this, it would be the equivalent to git subrepo push --tag --all --force. Am I correct? If so I prefer calling out all the parameters to --tag-refresh.