The database models include an Active boolean for both Entrypoint and Target entities, but the web UI provides no way to:
Toggle active/inactive on entrypoints or targets
Delete individual entrypoints or targets
Once an entrypoint or target is created, the only way to remove it is to delete the entire webhook. This means users cannot:
Temporarily disable a target without losing its configuration
Remove a misconfigured target without deleting everything
Deactivate an entrypoint to stop accepting events from a specific source
The README documents that inactive entrypoints should return HTTP 410 Gone, and the handler code does check entrypoint.Active, but there's no way to set an entrypoint to inactive via the UI.
Fix
Add UI controls and corresponding handlers for:
Toggle active/inactive on entrypoints (e.g., POST /source/{id}/entrypoints/{epID}/toggle)
Toggle active/inactive on targets (e.g., POST /source/{id}/targets/{targetID}/toggle)
Delete individual entrypoints (e.g., POST /source/{id}/entrypoints/{epID}/delete)
Delete individual targets (e.g., POST /source/{id}/targets/{targetID}/delete)
Category
Should-fix for usability.
## Bug
The database models include an `Active` boolean for both `Entrypoint` and `Target` entities, but the web UI provides no way to:
1. **Toggle active/inactive** on entrypoints or targets
2. **Delete individual** entrypoints or targets
Once an entrypoint or target is created, the only way to remove it is to delete the entire webhook. This means users cannot:
- Temporarily disable a target without losing its configuration
- Remove a misconfigured target without deleting everything
- Deactivate an entrypoint to stop accepting events from a specific source
The README documents that inactive entrypoints should return HTTP 410 Gone, and the handler code does check `entrypoint.Active`, but there's no way to set an entrypoint to inactive via the UI.
## Fix
Add UI controls and corresponding handlers for:
1. Toggle active/inactive on entrypoints (e.g., `POST /source/{id}/entrypoints/{epID}/toggle`)
2. Toggle active/inactive on targets (e.g., `POST /source/{id}/targets/{targetID}/toggle`)
3. Delete individual entrypoints (e.g., `POST /source/{id}/entrypoints/{epID}/delete`)
4. Delete individual targets (e.g., `POST /source/{id}/targets/{targetID}/delete`)
## Category
Should-fix for usability.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Bug
The database models include an
Activeboolean for bothEntrypointandTargetentities, but the web UI provides no way to:Once an entrypoint or target is created, the only way to remove it is to delete the entire webhook. This means users cannot:
The README documents that inactive entrypoints should return HTTP 410 Gone, and the handler code does check
entrypoint.Active, but there's no way to set an entrypoint to inactive via the UI.Fix
Add UI controls and corresponding handlers for:
POST /source/{id}/entrypoints/{epID}/toggle)POST /source/{id}/targets/{targetID}/toggle)POST /source/{id}/entrypoints/{epID}/delete)POST /source/{id}/targets/{targetID}/delete)Category
Should-fix for usability.