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
In a repo we recently found a way, that a user creates a PR in a fork with the title Dependabot/pip/pylint 3.2.7 and proper branch name and dependabot happily hops on the PR, rebases it, etc. even if the PR was never created by it.
This is especially nasty, since some issues like #3253 suggest to use github.actor == 'dependabot[bot]' which still evaluates to true, because the latest commit comes from dependabot but the rest of the code does not.
Is there a way to limit dependabot interaction to its own PRs?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
In a repo we recently found a way, that a user creates a PR in a fork with the title
Dependabot/pip/pylint 3.2.7and proper branch name and dependabot happily hops on the PR, rebases it, etc. even if the PR was never created by it.This is especially nasty, since some issues like #3253 suggest to use
github.actor == 'dependabot[bot]'which still evaluates to true, because the latest commit comes from dependabot but the rest of the code does not.Is there a way to limit dependabot interaction to its own PRs?
Beta Was this translation helpful? Give feedback.
All reactions