<!-- Please check [open issues](https://github.com/FCP-INDI/C-PAC/issues) before adding a new feature request. If something like your request already exists, please add to that discussion. --> **Related problem** <!-- Is your feature request related to a problem? Please describe, or delete this section entirely. A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]. If any open issues relate to the problem, please link to them here. --> We have to manually trigger the build of a new version of docs each time we release. **Proposed feature** <!-- Describe the solution you'd like. A clear and concise description of what you want to happen. --> All that needs to happen is 1. Check out the `source` branch of this repository. 2. Tag the HEAD with `v{semver}-source` with `v{semver} == ` the tag of the new release of [C-PAC](https://github.com/FCP-INDI/C-PAC). 3. Push the tag to this repository. A GitHub action is probably the simplest route to automate this behavior. **Alternatives** <!-- Describe alternatives you've considered, or delete this section entirely. A clear and concise description of any alternative solutions or features you've considered. --> * CircleCI * Travis
Related problem
We have to manually trigger the build of a new version of docs each time we release.
Proposed feature
All that needs to happen is
sourcebranch of this repository.v{semver}-sourcewithv{semver} ==the tag of the new release of C-PAC.A GitHub action is probably the simplest route to automate this behavior.
Alternatives