Currently, if a PR is landed into master, other protected branches (otakaro_digital_twin) can become out of date.
It would be good to include a step in one of the GitHub Actions, perhaps in build_documentation.yml or after the jobs listed there.
This new CI feature would automatically attempt to pull master into otakaro_digital_twin using merge, and if successful push to otakaro_digital_twin.
If it is not successful, it would raise an error.
This is suitable for someone new to GitHub Actions, but it is worth discussing with someone more familiar before beginning.
The easiest workaround until this is created is for someone with access to @GRI-Admin to switch to that account and open a PR from master into otakaro_digital_twin and land it
Currently, if a PR is landed into master, other protected branches (otakaro_digital_twin) can become out of date.
It would be good to include a step in one of the GitHub Actions, perhaps in
build_documentation.yml
or after the jobs listed there. This new CI feature would automatically attempt to pull master into otakaro_digital_twin using merge, and if successful push to otakaro_digital_twin.If it is not successful, it would raise an error.
This is suitable for someone new to GitHub Actions, but it is worth discussing with someone more familiar before beginning.