Nudge users to re-enable prebuilds if webhook has been disabled for GitLab projects
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13.8k
- Forks
- 1.4k
- Avg merge
- 17h 58m
- Merged PRs (30d)
- 5
Description
Problem to solve
GitLab automatically disabled prebuilds when the webhook is failing intermittently and is temporarily disabled.
See relevant docs about failing webhooks from GitLab:
If a webhook fails repeatedly, it may be disabled automatically.
If the hook continues to fail, the back-off period is extended on each retry, up to a maximum disabled period of 24 hours.
See relevant discussion (internal).
Proposal
Nudge users to re-enable prebuilds if webhook has been disabled for GitLab projects.
This could probably be resolved with an alert component at the top of the prebuilds list like the proposal in https://github.com/gitpod-io/gitpod/issues/9232 when prebuild are paused.
TBD (To be discussed)
Contributor guide
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 reviewing the proposal in issue 9232 and the prebuilds list referenced here. Clarify the alert's behavior and scope for GitLab projects whose webhooks are disabled; done should include an agreed design and a user nudge to re-enable prebuilds.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- gitlab, typescript
- Domain
- developer-experience, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100