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
Is your feature request related to a problem? Please describe.
With Depfu, rubocop is updated frequently and with these updates, the file .rubocop_todo.yml has to be regenerated since cops are often added/deleted/changed. We need to remember about regenerating this file. This can be sometimes forgotten.
Describe the solution you'd like
I would like that the CI regenerates the file .rubocop_todo.yml, so that it cannot be forgotten before the pull request is merged. In CircleCI, it is possible to have conditional jobs. With these, we can easily trigger the regeneration of the file .rubocop_todo.yml for the Depfu pull requests updating rubocop.
Describe alternatives you've considered
I contacted Depfu to ask them if it is possible to do this upstream and they told me that it isn't.
Is your feature request related to a problem? Please describe.
With Depfu, rubocop is updated frequently and with these updates, the file
.rubocop_todo.yml
has to be regenerated since cops are often added/deleted/changed. We need to remember about regenerating this file. This can be sometimes forgotten.Describe the solution you'd like
I would like that the CI regenerates the file
.rubocop_todo.yml
, so that it cannot be forgotten before the pull request is merged. In CircleCI, it is possible to have conditional jobs. With these, we can easily trigger the regeneration of the file.rubocop_todo.yml
for the Depfu pull requests updating rubocop.Describe alternatives you've considered
I contacted Depfu to ask them if it is possible to do this upstream and they told me that it isn't.
Additional context
Here's a link to the documentation for the conditional jobs
The text was updated successfully, but these errors were encountered: