No description
c6f4d4328b
There is a subtle bug in how the git module currently works. If the version you request is a tag name, and you've already got the repo cloned, and the tag name is a new tag, but refers to the already checked out working copy, the git module would exit early without change. This is bad as it means the new tag ref was not fetched and could not be used in later tasks. This change will check if the version is a remote tag, and if the tag doesn't exist locally. If that is true, it'll do a fetch. The activity could still be seen as not a change, because the working copy won't be updated, if the new tag refers to the already checked out copy, but that's not different than before and can be fixed as a more comprehensive overhaul of tracking change in the git module. |
||
|---|---|---|
| cloud | ||
| commands | ||
| database | ||
| files | ||
| internal | ||
| inventory | ||
| messaging | ||
| monitoring | ||
| net_infrastructure | ||
| network | ||
| notification | ||
| packaging | ||
| source_control | ||
| system | ||
| utilities | ||
| web_infrastructure | ||