Currently we've got https://github.com/maidsafe/QA/blob/master/Bash%20Scripts/Travis/after_success.sh#L10-L15 which restricts docs/tag generation to destination branch "master". This ofc prevents any new version change patches going to branches from creating a corresponding tag/documentation for the patch version.
Probably needs a bit of thought to get this in place and also not end up triggering a duplicate docs/tag build when just creating a new branch / merging from master
Currently we've got https://github.com/maidsafe/QA/blob/master/Bash%20Scripts/Travis/after_success.sh#L10-L15 which restricts docs/tag generation to destination branch "master". This ofc prevents any new version change patches going to branches from creating a corresponding tag/documentation for the patch version.
Probably needs a bit of thought to get this in place and also not end up triggering a duplicate docs/tag build when just creating a new branch / merging from master