rockdove

filter & redirect github webhooks

configuration

the following environment variables are required:

• GITHUB_WEBHOOK_SECRET: the secret you chose when you created the json webhook
• DISCORD_WEBHOOK: the regular discord webhook url
• DISCORD_BOT_WEBHOOK: the discord webhook url for bot-authored events
• DISCORD_USERSTYLES_WEBHOOK: the discord webhook url for all non-bot events on catppuccin/userstyles.
• DISCORD_ERROR_WEBHOOK: the discord webhook url for errors

the following environment variables are optional:

• PORT: the port to listen on (default: 3000)

development

To learn how to forward webhook events to a local instance of rockdove, follow the instructions below:

1. Ensure your .envrc has the environment variables listed above in the configuration section.

2. Compile a release build of rockdove and run it:

   cargo build --release
   ./target/release/rockdove
   

3. Install the gh cli webhook forward extension:

   gh extension install cli/gh-webhook
   

4. Allow gh cli to create organisation webhooks on your behalf:

   gh auth refresh -h github.com -s admin:org_hook
   

5. Forward the webhook events to your local instance of rockdove:

   gh webhook forward --events='*' --org=catppuccin --url="http://localhost:3000/webhook"
   

6. Finally, visit the GitHub webhook settings and paste the GITHUB_WEBHOOK_SECRET into the newly created development webhook.

cutting a release

Follow the steps below, replacing <tag> with the version (e.g. 2.1.0) you want to publish:

1. Generate your changelog:

   git cliff --unreleased --tag <tag> --prepend CHANGELOG.md
   

2. Update your Cargo.toml with the new version, and make sure to rebuild to force the Cargo.lock to regenerate.

3. Add, commit and push your changes, the commit message is important so that git cliff doesn't include it in future changelogs:

   git commit -am "chore(release): prepare for v<tag>"
   git push
   

4. Create the tag and push your changes

   git tag -a v<tag> -m "v<tag>"
   git push origin v<tag>