Service user for GitHub #186
Assignees
Comments
|
We now have the email address [email protected], so a service user could be registered using this address |
|
Instead of a service user, we created a GitHub app: https://github.com/apps/pulumi-kotlin |
Merged
jplewa
added a commit
that referenced
this issue
Jul 13, 2023
## Task Resolves: #194 #186 ## Description I added the action defined in `update_schemas.yml` which will periodically check if new versions of any of the schemas are available. It will then open a pull request. Two additional changes were made: - Both this action as well as the cleanup step in `prepare_release.yml` (which also opens a PR) will now rely on GitHub application tokens. I followed [this tutorial](https://github.com/peter-evans/create-pull-request/blob/main/docs/concepts-guidelines.md#authenticating-with-github-app-generated-tokens) to create this application and I'm waiting for the VirtuslabRnD admins to approve it to be added to this repository. Pull requests created by an app should trigger CI builds. - ~~I added an extra action defined in `publish_to_maven_local_before_release.yml`. It's a duplicate of `publish_to_maven_local.yml` but with a different condition (it will be triggered by a pull request when its source branch matches the regex `prepare-release-.*`).~~ EDIT: I changed this. The action defined in `publish_to_maven_local.yml` should now get triggered on push to main, on workflow dispatch, and on pull request **if the source branch has the appropriate name**.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We can't use the default
github-actionsuser, because its commits do not trigger CI (see example PR here: #183).Issue on GitHub: peter-evans/create-pull-request#48
Do
pulumi-kotlin-botvirtuslabrndorganization by raising a support ticketjvm-labteam (anyone from @VirtuslabRnD/jvm-lab team should be able to do it, or @myhau )cleanupstep inprepare_release.ymlso that automatic pull requests will now be opened by the service user (this can probably be done by configuring theauthorand/orcommitterproperties in https://github.com/peter-evans/create-pull-request)Future stuff
With a service user like this, we could automate the releases of new schemas. We would just need to run
./gradlew prepareReleaseOfUpdatedSchemason some cron schedule and create a PR if any changes are made (similarly as in thecleanupstep inprepare_release.yml)The text was updated successfully, but these errors were encountered: