Gitea automerge fails because of branchStatus "yellow" #15853
-
|
Hi everyone, The PR shows that automerge is enabled, renovate also seems to check and would "want" to automerge. I still end up getting "no automerge" although I can see in the gitea frontend that the latest commit ran fine on Jenkins (tests are present) and I also approved the PR (which is opened by another that has also has write permissions and could merge the branch/PR. I set the logs to I'm wondering: is this an issue I should report to the gitea project, i.e. is this a problem in their API or is this a bug in renovate? |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 4 replies
-
|
Please find and read their API reference for this endpoint. |
Beta Was this translation helpful? Give feedback.
-
|
I checked with the public gitea demo API and it worked as expected. So the problem seems to be specific to the gitea setup I'm working with, so I will address it there. |
Beta Was this translation helpful? Give feedback.
-
I had the same problem. I also noticed, that manual branches (without slashes in them) did give me results via the API. Also I suspect the underlying problem is similar to the emoji-thing (#10264 (comment)), and here might also be some gitea-mysql-encoding error in the background, which is silently ignored. My solution was simply to change the branch-prefix from "renovate/" to "renovate_" and then closing all existing branches PRs to forces them to be recreated. On a side note: Be sure to have branch-protection in place, because otherwise you may see some premature merges (see #2948) |
Beta Was this translation helpful? Give feedback.
Please find and read their API reference for this endpoint.