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
It looks like @renovate-bot has been pushing hundreds of commits directly to the default branch. These look to be repeats of the same pair of commits that alternately add and remove lines from package-lock.json related to yargs-parser.
Is it unintentional that this bot is configured to push directly to the default branch (without opening a pull request)? Even if this is intentional, it looks like the repeated commits regarding yargs-parser are an indication of something broken.
Many thanks for the heads up, @tschaub! The rogue commits are now gone, and I'll keep an eye out in case they recur.
I did indeed configure this bot so that if there are no conflicts, it can push directly to the default branch. Looks like it might be worth revisiting that decision...
It looks like @renovate-bot has been pushing hundreds of commits directly to the default branch. These look to be repeats of the same pair of commits that alternately add and remove lines from
package-lock.json
related toyargs-parser
.Is it unintentional that this bot is configured to push directly to the default branch (without opening a pull request)? Even if this is intentional, it looks like the repeated commits regarding
yargs-parser
are an indication of something broken.cc @hegemonic
The text was updated successfully, but these errors were encountered: