-
Notifications
You must be signed in to change notification settings - Fork 88
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
Pull request creation fails #282
Comments
I have the impression Azure is having issues so it can be related. |
My team is also seeing this issue in our winget workflows. |
@JanDeDobbeleer, I just tried submitting a manifest and it was successful. Could you try again and let me know? We haven't made any changes or pushed out any recent releases so I'm thinking it could be a one-off. |
I'm still seeing the same issue here. |
@ryfu-msft the problem persists. |
@JanDeDobbeleer, have you already tried fetching new commits and merging them into your fork's master branch? I suspect you are possibly encountering issue #234 again. |
@ryfu-msft correct, updating my master branch makes everything work again. That does mean that the previous fix on your end no longer works, right? For anyone else, how to update your master branch: git remote add upstream git@github.com:microsoft/winget-pkgs.git
git switch master
git reset upstream/master --hard
git push On another note, can we rename master to main one day? It's 2022 after all ;-) |
@ryfu-msft Is there an open issue for this? Expecting users to know to update their master branch when they get an |
@kevinoid, yes, you are correct. I will address that in a bug fix soon and report an appropriate error message. I will also need to take another look at my previous fix from #235. I verified this multiple times during implementation, but it seems like after a certain number of commits behind, it fails to perform the update. |
Thanks @ryfu-msft, I appreciate it! |
I came accross the same problem. FWIW: 'Fetch and Merge' is a workaround, that worked for me: |
Unfortunately, fetch and merge wont work if its too far behind or if there are conflicts that require manual intervention |
I have the same issue, did anyone have a fix? |
Brief description of your issue
Submitting a PR fails with the following error:
Steps to reproduce
Submit a PR ;-)
Expected behavior
It submits the PR
Actual behavior
It fails at submitting the PR
Environment
The text was updated successfully, but these errors were encountered: