As described in the ePO workflow documentation (to be published), at the beginning of the process of creating a new ePO release, the product owner ( OP-TED) performs a number of manual actions related to Github:

• Assignment of a selection of GitHub Issues with a milestone related to the new release.
• Creation of 3 "release" branches:

1. One on the OP/epo-conceptual-model repository, where the Conceptual Model and the SDS artefacts will be created and can be reviewed.
2. One on the OP/ePO repository, where the SDS artefacts to be published as a stable release will be moved once reviewed.
3. One on the OP/ePO-docs where the contents of the website containing the SDS documentation will be moved and/or generated.

• Other optional manual actions may happen such as creating a project containing the related github issues of the release, or even a section in "discussions" dedicated to the release.

To investigate if it is worth replacing all the above actions with a Github Action