chore: github action master to rel/rc

[mmcshinsky-bitgo]

Create automatic pull request from master to rel/rc whenever master is updated.

BG-49173

[ducnguyen-bitgo]

I tested the action in my own private repo and it seemed to work correctly. Everything looks good to me!

[tylerlevine]

I like the idea, but please create a jira for this instead of using BG-00000 so we can track it as part of the sprint. That fake ticket number shouldn't really ever be used and if it is, it should be for quick fixes and not net new features.

Also, is this going to create signed commits? Note that the repo requires all commits to be signed (but a signature from Github is acceptable).

Other than that, just some minor improvement suggestions.

[tylerlevine]

Suggested change

BG-000000

[mmcshinsky-bitgo]

Can do!

[mmcshinsky-bitgo]

I wonder if we can set something up like this? https://github.com/marketplace/actions/jira-create-issue

[tylerlevine]

I'm confused why we check out rel/rc, then fetch and hard reset to master - why not just check out master directly?

[mmcshinsky-bitgo]

It came from this example here: https://github.com/peter-evans/create-pull-request/blob/main/docs/examples.md#keep-a-branch-up-to-date-with-another

[ducnguyen-bitgo]

We could either checkout `rel/rc` or specify it as `base` in `Create Pull Request` (CPR) according to the CPR docs.

[mmcshinsky-bitgo]

I've played around with a few different configurations on a private repo and the current one in the PR is the only one that properly triggers the pull request for me.

[ducnguyen-bitgo]

Just left a couple of comments on how the create pull request action plugin should work. Otherwise, everything looks good to me! Btw, I haven't looked at why one of the checks failed.