Change strategy to create PRs in downstream repos

rgildein commented 3 weeks ago

Part of our initiative of improving central file management is to improve our process in this automatization. The idea is that instead of create PRs in downstream repos after PR in this repo is created, we should create PRs straight forwards.

So instead, the workflow will change the following way:

Create Draft PR -> CI trigger and user can see the output, without PRs in downstream being created
convert Draft to regular PR -> PRs in downstream will be created
reviewer check also PRs in downstream and approve only if workflows do not crash due to some type etc.
[optional] After PR in this repo is closed, another CI could enable auto-merge in downstream repos and provide approval from the bot. If CI passes, the downstream repos will be merged automatically.

Prerequisite is that all downstream PRs are linked with original repo (the original PR is mention in the downstream, so GitHub would do rest).

related: #52

syncronize-issues-to-jira[bot] commented 3 weeks ago

Thank you for reporting us your feedback!

The internal ticket has been created: https://warthogs.atlassian.net/browse/SOLENG-844.

This message was autogenerated

rgildein commented 2 weeks ago

It was fixed by #112, however for now no auto-merge.

canonical / solutions-engineering-automation

Change strategy to create PRs in downstream repos #111