Skip to content
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

Rogue renovate-bot #1912

Closed
tschaub opened this issue May 4, 2021 · 2 comments
Closed

Rogue renovate-bot #1912

tschaub opened this issue May 4, 2021 · 2 comments

Comments

@tschaub
Copy link
Contributor

tschaub commented May 4, 2021

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.

cc @hegemonic

@tschaub
Copy link
Contributor Author

tschaub commented May 4, 2021

It looks like this is described at yargs/yargs-parser#363 (comment).

The @renovate-bot folks have deployed a workaround. See renovatebot/renovate#9837 (reply in thread).

@hegemonic
Copy link
Contributor

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...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants