-
Notifications
You must be signed in to change notification settings - Fork 160
feat(release-brancher): add argument to override pull request title #2615
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
b3d0f69
to
6f3264a
Compare
"go-yoshi", | ||
"java-bom", | ||
"java-lts", | ||
"java-lts-on-patch", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is better than "java-lts-no-sp".
My command-line fails with trying to create non-existent 'main' branch of my repository (https://api.github.com/repos/suztomo/google-http-java-client/branches/main).
|
The default branch name has become "main" from "master" in code-suggester. |
Created #2618 to address the problem. |
6f3264a
to
8f594fa
Compare
8f594fa
to
9583104
Compare
Now #2618 is merged. |
} | ||
} | ||
const message = 'feat: configure initial sp version'; | ||
const message = 'feat: configure the protected branch'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@chingor13 Does "configure initial sp version" have special effect somewhere? In past (https://github.com/googleapis/repo-automation-bots/pull/1674/files#diff-4b2e8d3f62c327048db13c5f552d94303eac7ed241728c5fd5dbc3e5842961c9R327), you updated this message from 'ci: setup workflows for new release branch' to 'feat: configure initial sp version'.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In this case, any releasable commit (feat
, fix
, etc, will trigger a new library release). For the -sp versions, we wanted to force a release. For the new backport releases, we don't need to force a new release, so ci
is probably a better message.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Created #2622 (review)
"go-yoshi", | ||
"java-bom", | ||
"java-lts", | ||
"java-backport", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Now it's "java-backport"
"ci / docs" failed but I believe it's irrelevant.
|
🤖 I have created a release \*beep\* \*boop\* --- <details><summary>@google-cloud/release-brancher: 1.3.0</summary> ### Features * **release-brancher:** add argument to override pull request title ([#2615](https://www.github.com/googleapis/repo-automation-bots/issues/2615)) ([1f952c7](https://www.github.com/googleapis/repo-automation-bots/commit/1f952c73eba10bc8eedc5c5a16944622b8e84c46)) ### Bug Fixes * **release-brancher:** provide default branch name for PRs ([#2618](https://www.github.com/googleapis/repo-automation-bots/issues/2618)) ([24a15a8](https://www.github.com/googleapis/repo-automation-bots/commit/24a15a89a76e15153f0e6cce2c7d69d97464df5c)) </details> This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
Use "ci: " suffix in the commit message when it creates a workflow pull request for initializing the protected branch. This addresses @chingor13 's comment in #2615 (comment) Fixes #2568 🦕
Fixes #2568
My manual test
It worked
It created suztomo/google-http-java-client#16 and suztomo/google-http-java-client#15
Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:
Fixes #2568 🦕