Skip to content

feat: trigger audited webhook pings - #240

Open
giscebot wants to merge 1 commit into
feat/webhook-socket-ingressfrom
feat/webhook-ping-action
Open

giscebot wants to merge 1 commit into
feat/webhook-socket-ingressfrom
feat/webhook-ping-action

Conversation

@giscebot

@giscebot giscebot commented Oct 5, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

  • add an administrator-only action to request a fresh GitHub webhook ping
  • validate the stored URL against the exact api.github.com organization/repository hook path before invoking gh api
  • audit requested, successful and failed ping actions with the administrator identity
  • keep operational CLI errors out of browser responses
  • add a Send ping control, progress feedback, delayed refresh and recent administrative actions to hook detail
  • document required webhook write permissions for the operational GitHub identity

Validation

  • pytest -q — 410 passed
  • npm test -- --run — 62 passed
  • npm run build

Refs #191

Requested by: @ecarreras

Let dashboard administrators request a fresh GitHub hook ping through the operational gh identity. Validate the stored API path, audit every result, refresh hook details, and avoid exposing CLI failures to the browser.\n\nRefs #191\n\nCo-authored-by: Eduard Carreras <ecarreras@gisce.net>
@giscebot
giscebot added this pull request to stack #235 October 5, 2026 09:42
@giscebot
giscebot requested a review from ecarreras October 5, 2026 09:43
@giscebot giscebot self-assigned this Oct 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant