feat: add autorelease.trigger command#314
Merged
SurferJeffAtGoogle merged 15 commits intogoogleapis:masterfrom Apr 28, 2021
Merged
feat: add autorelease.trigger command#314SurferJeffAtGoogle merged 15 commits intogoogleapis:masterfrom
SurferJeffAtGoogle merged 15 commits intogoogleapis:masterfrom
Conversation
google-cla
Bot
added
the
cla: yes
Contributor
|
How easy would it be to make it handle the GoogleCloudPlatform org as well as googleapis? Basically if now is a good time to fix #287 that would be great :) |
Contributor
Author
SurferJeffAtGoogle
suggested changes
Apr 26, 2021
| @@ -0,0 +1,125 @@ | |||
| # Copyright 2021 Google LLC | |||
SurferJeffAtGoogle
approved these changes
Apr 28, 2021
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This trigger will run on a cron. It will scan the googleapis org for merged pull requests with
autorelease: taggedlabels. For each found pull request, it will trigger the associated Kokoro job.Implementation-wise, it's essentially the same workflow as the tag job, but looks for a different label and only handles the kokoro triggering (no tagging).