Thank you for considering a contribution—your help keeps this repository healthy for every bobrapet Story.
This guide explains how we work in the github-webhook-impulse repository, from filing issues to sending patches.
- Search for an existing report under Issues.
- If nothing matches, open a new issue with a clear description, reproduction steps, and both observed and expected behaviour.
- Start a thread in Discussions or file a feature request issue.
- Document motivating use-cases, proposed config additions, and any compatibility considerations for existing Stories.
- Fork the repository and branch from
main. - Keep changes focused; additive config should include manifest updates (
Engram.yamlorImpulse.yaml) and README documentation. - Run the quality gates locally:
make lintmake testmake docker-build IMG=ghcr.io/<your-user>/github-webhook-impulse:devwhen binaries or Dockerfile paths change
- Open the PR with a summary, testing evidence, and any follow-up TODOs.
- Go 1.26+
- Docker (or another OCI-compatible builder)
make
- Fork the repository.
- Clone your fork:
git clone https://github.com/<your-user>/github-webhook-impulse.git - Enter the repo:
cd github-webhook-impulse - Install tooling:
make lint-config - Confirm builds and tests:
make build && make test
make testWe use Conventional Commits so releases and change logs stay automated.
Examples:
feat: add new configuration optionfix: handle edge case in processingdocs: clarify configuration fieldschore: bump SDK to latest
Participation in this project is governed by the Contributor Covenant Code of Conduct. Report unacceptable behaviour to conduct@bubustack.com.