-
Notifications
You must be signed in to change notification settings - Fork 364
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
feat(operations): split the operations-per-run option between queries and mutations #501
feat(operations): split the operations-per-run option between queries and mutations #501
Conversation
0936a35
to
78dc715
Compare
78dc715
to
362cdf7
Compare
362cdf7
to
acd609a
Compare
up |
acd609a
to
8745539
Compare
up |
bf103bc
to
c3c7dca
Compare
Make sure to log the warning about the overflow of operations when the process fail fast due to a lack of operations as well as when it's finished as expected BREAKING CHANGE: the operations per run option no longer exists and was replaced by the query and mutation ones
e790815
to
72c9c80
Compare
@luketomlinson would be nice if you could review/merge this one and later create the next major release. |
@luketomlinson bump and also if you can create a new release it would be nice (maybe go for 4.1) then merge this one if you think it's a good PR then let it idle and create a v5 later. WDYT? |
It's sad to see good work go to waste like this. |
Changes
operations-per-run
optionquery-operations-per-run
(to read) andmutation-operations-per-run
(to alter the issues) options, resolves Feature request: option to limit mutations per run #495Context
For huge projects, it can be scary to process all the issues with this action, especially when it's the first configuration.
The operations-per-run was covering all kind of operations and was helpful, but not enough to process the whole set of issues without changing everything.