regro / rever

Releaser of Versions
https://regro.github.io/rever-docs/
BSD 3-Clause "New" or "Revised" License
74 stars 34 forks source link

BUG: track which remote got tagged #44

Open CJ-Wright opened 7 years ago

CJ-Wright commented 7 years ago

One may want to run a trial run tag against a remote that is not production (I certainly did as I didn't want to mess things up on my first outing with rever). Currently this won't work since if the log is not git tracked then it will know that the tag was successful (at least against the other remote). Also we might aim to be as verbose as possible in the logs anyway just for the sake of provenance.

scopatz commented 7 years ago

Yes, this is a good point. I was copying the repo over to new dir on the file system and messing with that. There is probably a more elegant solution to trying rever out and performing dry runs.