Closed galdinorosas closed 4 years ago
hard to tell what is wrong. But maybe you can look in how it's solved in https://github.com/tibdex/github-rebase? It's using @octokit/rest
internally
I appreciate the link, i'll look into it.
From your own personal opinion, what octokit API would you suggest to update my local pull request head branch with a forked upstream base branch?
Thanks
On Oct 9, 2019, at 16:42, Gregor Martynus notifications@github.com wrote:
hard to tell what is wrong. But maybe you can look in how it's solved in https://github.com/tibdex/github-rebase? It's using @octokit/rest internally
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
@galdinorosas I'm very sorry I missed your follow up question!
Did you figure it out? I don't think that there is a single API call to make that work, it would be a bit more complex. But it sounds like a problem others might run into, maybe it would be worth to create a plugin?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
I was told from github developers to use "/repos/:owner/:repo/merges" to update a stale pull request head branch. This is my request params i send:
The error I am getting is a 404 Head Does Not Exist but I know the base branch contains this latest sha. The crazy thing is that this error seems intermittent. Should I be updating my stale PR head branches in a different way?
Please let me know.
Thank You
Proof that the base pull request branch has the latest sha: