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
I deleted the branch, noticed that it should be backported and added the label. Since that didn't immediately work, I restored the branch and re-applied the label.
This could just be an error of impatience on my end but I wanted to make sure.
I'm not well versed enough in JS to figure out how exactly the ref to be backported is fetched here but if you're fetching the source branch from the fork, perhaps look into fetching refs/pull/$num/head on the source repo itself instead.
The text was updated successfully, but these errors were encountered:
Deletion of the branch is definitely a problem of the current approach. I've also been thinking about how to deal with #46 and fetching refs/pull/$num/head might be the solution for both issues. However, that requires a larger change which I've been postponing a bit, but I really want to get started on. I have some ideas and I know how to validate these, but it takes time. Fixing these will push the action out of early-development and into version 0.1.x range IMO.
@Atemu Problem should be resolved with the latest master. I'll probably release a new version soon as well, but please be aware that you can already try this fix by using master or 3359d57. With #162 it is now also no longer necessary to set fetch-depth: 0 for the actions/checkout@v2 action.
This may just have happened in NixOS/nixpkgs#129258.
I deleted the branch, noticed that it should be backported and added the label. Since that didn't immediately work, I restored the branch and re-applied the label.
This could just be an error of impatience on my end but I wanted to make sure.
I'm not well versed enough in JS to figure out how exactly the ref to be backported is fetched here but if you're fetching the source branch from the fork, perhaps look into fetching
refs/pull/$num/head
on the source repo itself instead.The text was updated successfully, but these errors were encountered: