gutenberg-mobile icon indicating copy to clipboard operation
gutenberg-mobile copied to clipboard

Add workflows for creating releases

Open jhnstn opened this issue 1 year ago • 4 comments

This adds two Github workflows to create release PRs

prepare-release.yml will create a release PR on this repo, Gutenberg Mobile

integrate-release.yml will create an integration release on the specified platform

Both take a release version and the option to specify a gbm-cli version (this can be a tag or a commit on release-toolkit-gutenberg-mobile )

As-is we will need to generate an access token and add it to this repository. There is a PAT_TOKEN there now but I'm not sure if it's still valid. We need a secret named 'GH_ACCESS_TOKEN` that has access to this repo for the prepare commands. The token will have to work with the main app repos for the integration workflow to work.

To test: Testing will get a bit noisy so it might be best to merge this branch into a fork of Gutenberg Mobile and add GBM_WPMOBILE_ORG and GBM_WORDPRESS_ORG: to the workflow env sections like so:

...
     env:
         GITHUB_TOKEN: ${{ secrets.GH_ACCESS_TOKEN }}
         GITHUB_USER: ${{ github.actor }}
         GBM_WPMOBILE_ORG: {your github user}
         GBM_WORDPRESS_ORG:  {your github user}
...

You will also need a github PAT added to the fork as a repository secret named GH_ACCESS_TOKEN

Then run the prepare worklfow with a version associated with a test release pr on your forked Gutenberg repo

The integration will only work for android in this scenario since iOS will require pods for the release.

PR submission checklist:

  • [ ] I have considered adding unit tests where possible.
  • [ ] I have considered if this change warrants user-facing release notes more info and have added them to RELEASE-NOTES.txt if necessary.

jhnstn avatar Nov 08 '23 22:11 jhnstn