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
mdanish-kh opened this issue
Jan 26, 2024
· 1 comment
· Fixed by #11865
Assignees
Labels
must-doIssues that must be completed by the end of the Sprint. Or else. Only humans may set this.s4Internal bugs (e.g. test flakes), extreme edge cases, and bug risks
Submitting pull request for manifest...
Unable to create a reference to the forked repository. This can be caused when the forked repository is behind by too many commits. Sync your fork and try again.
Error: Process completed with exit code 1.
Steps to fix
This will reproduce for subsequent releases/runs until the fork used for submitting PR is kept in sync with upstream.
Thanks a lot @mdanish-kh. I will fix this before the next release.
matifali
added
bug
s4
Internal bugs (e.g. test flakes), extreme edge cases, and bug risks
must-do
Issues that must be completed by the end of the Sprint. Or else. Only humans may set this.
and removed
chore
labels
Jan 26, 2024
must-doIssues that must be completed by the end of the Sprint. Or else. Only humans may set this.s4Internal bugs (e.g. test flakes), extreme edge cases, and bug risks
Description
Take a look at - https://github.com/coder/coder/actions/runs/7611646446/job/20727993997 (and other release runs)
Publishing to winget failed because:
Steps to fix
This will reproduce for subsequent releases/runs until the fork used for submitting PR is kept in sync with upstream.
i.e., https://github.com/cdrci/winget-pkgs in this case
WingetCreate does attempt to sync the fork before making a PR, but that can fail if the fork is behind too many commits.
Suggest to make it as part of CI to sync the fork (through
gh
CLI?) before winget publish step to avoid this in the futureUpstream issue
Related to:
The text was updated successfully, but these errors were encountered: