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'm currently using Read the Docs together with Codeberg which uses Forgejo (a fork of Gitea). I know, that there is no full support of Gitea, so I'm using the Generic things. using the incoming GitHub Webhook works for triggering builds, as described in the Documentation. But I also want to report the status of the Build to Codeberg. I'm trying to use the build status webhooks to call the Forgejo API. But thres ne big problem: The API endpoint want the commit in the Path, was is currently not possible.
Describe the solution you'd like
Allow using variables in the Webhook URl, so I can use something like https://codeberg.org/api/v1/repos/Owner/Repo/statuses/{{ build.commit }} as the URL.
Alternative solutions
I don't have a Idea for a Workaround.
Additional context
None
The text was updated successfully, but these errors were encountered:
What's the problem this feature will solve?
I'm currently using Read the Docs together with Codeberg which uses Forgejo (a fork of Gitea). I know, that there is no full support of Gitea, so I'm using the Generic things. using the incoming GitHub Webhook works for triggering builds, as described in the Documentation. But I also want to report the status of the Build to Codeberg. I'm trying to use the build status webhooks to call the Forgejo API. But thres ne big problem: The API endpoint want the commit in the Path, was is currently not possible.
Describe the solution you'd like
Allow using variables in the Webhook URl, so I can use something like
https://codeberg.org/api/v1/repos/Owner/Repo/statuses/{{ build.commit }}
as the URL.Alternative solutions
I don't have a Idea for a Workaround.
Additional context
None
The text was updated successfully, but these errors were encountered: