matrix-org / matrix-org/matrix-hookshot
Support seperate webhook secrets for GitLab instances / repositories
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 450
- Forks
- 95
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 23
Description
https://github.com/Half-Shot/matrix-hookshot/blob/0c4b911a705f464d0a1edb51b2181845c4894b14/docs/setup/gitlab.md#L21
This isn't explained at all. I suspect you're supposed to enter it into this "Secret Token" field on GitLab?
Is it required? It would be nice if GitLab instanced could be user-defined, and also their secrets. If above assumption is correct, then the secret would also be shared across all instances, which isn't great.
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 with docs/setup/gitlab.md around line 21 and trace the GitLab webhook configuration it describes. Confirm how the Secret Token is currently interpreted, then scope per-instance and per-repository secrets and document when they are required. Done means the requested separation is supported and the setup guidance is unambiguous.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend-api-design, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100