-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Update Dependencies automation always force pushes a rewritten commit #5397
Labels
Comments
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label. |
[Triage] This also means that the automation doesn't handle updating changes to an existing branch very well - they always get overwritten or the change gets skipped. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
See this PR for example: #5393
It makes one commit with its updates, and then appears to force push changes that include updates from the base branch. See the diff for the force push: https:/dotnet/dotnet-docker/compare/71a84714b0f607a4e1796cee8afda87a3581644c..255c35ffae79ada42267f9bc1d5b00e50f3cee84?diff=unified&w=
This should just be one commit based on top of the latest commit from the base branch.
The text was updated successfully, but these errors were encountered: