Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Pushes to master should trigger merges and pushes to other protected branches #191

Open
LukeParky opened this issue Jul 15, 2024 · 1 comment · May be fixed by #244
Open

Pushes to master should trigger merges and pushes to other protected branches #191

LukeParky opened this issue Jul 15, 2024 · 1 comment · May be fixed by #244
Labels
AA - Non Functional Non-Functional requirements (Quality or Security or Tech Debt) devops/ci/cd Related to automate deployment, or other systems work good first issue Good for newcomers
Milestone
Sprint 5 (Sep 27)

Comments

@LukeParky
Copy link
Member

LukeParky commented Jul 15, 2024 •
edited
Loading

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.
@LukeParky LukeParky changed the title Pushes to master should trigger merges and pushes to other protected branches, namely otakaro_digital_twin Pushes to master should trigger merges and pushes to other protected branches Jul 15, 2024
@LukeParky LukeParky added good first issue Good for newcomers devops/ci/cd Related to automate deployment, or other systems work labels Jul 15, 2024
@LukeParky
Copy link
Member Author

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

@Martin20494 Martin20494 linked a pull request Sep 13, 2024 that will close this issue
Open
19 tasks
@Martin20494 Martin20494 linked a pull request Sep 13, 2024 that will close this issue
191 pushes to master should trigger merges and pushes to other protected branches #244
Open
19 tasks
@LukeParky LukeParky added the AA - Non Functional Non-Functional requirements (Quality or Security or Tech Debt) label Sep 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
AA - Non Functional Non-Functional requirements (Quality or Security or Tech Debt) devops/ci/cd Related to automate deployment, or other systems work good first issue Good for newcomers
Projects
None yet
Milestone
Sprint 5 (Sep 27)
2 participants
@LukeParky @Martin20494