liquidmetal-dev / liquidmetal-dev/microvm-action-runner
webhook check from github returns 500
Open
Nobody has claimed this yet.
kind/bug
- Dominant language
- Go
- Stars
- 6
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
When adding a new webhook pointing to the service, the ping from github results in a 500.
The service still works, just looks bad
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the webhook endpoint and reproducing the GitHub ping when adding a new webhook. Trace why the ping returns HTTP 500 while the service remains usable; done means GitHub's webhook check succeeds without changing normal service behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100