You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat: Support sequential-calls manifest field that disables concurrency when creating multiple pull requests or releases (#1401)
When running release-please on the google-cloud-ruby manifest, we're running afoul of secondary rate limits. Currently release-please runs pull request creation concurrently, and in this case, it was trying to open 33 pull requests at once which seemed to be too much. So we're introducing an option to run them sequentially using blocking calls.
This was added to the manifest config rather than the CLI options, because it seems to be a scaling-related knob that should be set per repository, rather than something that depends on how release-please is invoked.
I honestly do not know how to write a test for this. I tested manually both the sequential and concurrent cases to make sure the functionality was still correct, but I'm not sure how to test whether something happened concurrently or not.
Copy file name to clipboardExpand all lines: docs/cli.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -56,7 +56,6 @@ Extra options:
56
56
|`--draft-pull-request`|`boolean`| If set, create pull requests as drafts |
57
57
|`--label`|`string`| Comma-separated list of labels to apply to the release pull requests. Defaults to `autorelease: pending`|
58
58
|`--release-label`|`string`| Comma-separated list of labels to apply to the pull request after the release has been tagged. Defaults to `autorelease: tagged`|
59
-
|`--skip-labeling`|`boolean`| If set, labels will not be applied to pull requests |
60
59
|`--changelog-path`|`string`| Override the path to the managed CHANGELOG. Defaults to `CHANGELOG.md`|
61
60
|`--changelog-type`|[`ChangelogType`](/docs/customizing.md#changelog-types)| Strategy for building the changelog contents. Defaults to `default`|
62
61
|`--changelog-sections`|`string`| Comma-separated list of commit scopes to show in changelog headings |
@@ -83,6 +82,7 @@ Extra options:
83
82
| ------ | ---- | ----------- |
84
83
|`--config-file`| string | Override the path to the release-please config file. Defaults to `release-please-config.json`|
85
84
|`--manifest-file`| string | Override the path to the release-please manifest file. Defaults to `.release-please-manifest.json`|
85
+
|`--skip-labeling`|`boolean`| If set, labels will not be applied to pull requests |
86
86
87
87
### Without a manifest config
88
88
@@ -109,6 +109,7 @@ need to specify your release options:
109
109
|`--signoff`| string | Add [`Signed-off-by`](https://git-scm.com/docs/git-commit#Documentation/git-commit.txt---signoff) line at the end of the commit log message using the user and email provided. (format "Name \<email@example.com\>") |
110
110
|`--extra-files`|`string[]`| Extra file paths for the release strategy to consider |
111
111
|`--version-file`|`string`| Ruby only. Path to the `version.rb` file |
112
+
|`--skip-labeling`|`boolean`| If set, labels will not be applied to pull requests |
0 commit comments