fail sooner when PR creation data is incomplete #9888
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What are you trying to accomplish?
The PullRequestCreator refuses to create PRs when either the
previous_version
is absent or theprevious_requirements
reveal there were no changes to a dependency.That code is here:
dependabot-core/common/lib/dependabot/pull_request_creator.rb
Lines 224 to 231 in 75b4812
This results in what looks like successful runs ending with a PR not being created.
To improve this, we need to move the validation check closer to where the issue is. In this PR, I added behind an experiment the same check right before sending the PR data to the client.
This will give us, and customers, more information about the nature of the problem, since it will tell us which dependency is failing and why. Then we can target which ecosystems need help and see if we can fix them.
How will you know you've accomplished your goal?
We should start seeing the errors from the Updater side and track them in Sentry along with the dependency name and ecosystem.
Checklist