Jinx :: R-Ladies organizational guidance

Commands

Mon, 01 Jan 0001 00:00:00 +0000

The same /jinx commands work on GitHub and Slack. The difference is where the response goes – a GitHub issue comment or a Slack message. The canonical command list lives at /jinx help and is what Jinx shows when you ask /jinx help. Information commands These commands return the information directly. No GitHub issues are created. Command What it does /jinx help Show all available commands /jinx report weekly Org-wide activity summary (commits, PRs, issues) /jinx report monthly Same, for the past 30 days /jinx report chapters Chapter health: active vs inactive, months since last event /jinx gha-dashboard GitHub Actions CI status across all repos /jinx analytics Org-wide contributor and commit trends /jinx generate website analytics [period] Plausible website stats (7d/30d/month/6mo/12mo) /jinx contributors [repo] Contributor list for a repo /jinx contributors org Top contributors org-wide /jinx events Recent events for a chapter /jinx cfp list Open calls for proposals /jinx translate status Translation coverage across languages /jinx translate validate [lang] Check translation placeholders /jinx chapter-health Check chapter activity health /jinx blog-check-links Check all blog URLs for broken links Action commands These commands perform an action (create an issue, send an invite, post an announcement) and reply with a link to what was created.

Slash commands

Mon, 01 Jan 0001 00:00:00 +0000

Runs in: Cloudflare Worker (Slack slash entry) → GitHub Actions with the jinx-bot container (most commands) or Worker only (the four local commands). A /jinx ... invocation has two front doors: GitHub issue comments and Slack slash commands. Both end up running the same R package logic; the only difference is which event triggers it and where the answer is posted.

Asking Jinx a question

Mon, 01 Jan 0001 00:00:00 +0000

Runs in: Cloudflare Worker (worker/src/slack-events.js, worker/src/rag.js) + Cloudflare Vectorize + Workers AI. No GitHub Actions, no R package. When you DM Jinx in Slack, mention them in a channel, or use the Slack Assistant panel, your message is treated as a question – not a slash command. There is no /jinx prefix, no command to remember; just ask. Jinx searches a Cloudflare Vectorize index of RLadies+ content and replies with a grounded answer plus links to the sources it used. React to the answer with 👍 / 👎 / ❤️ and we collect that signal to track which answers are useful (see /jinx feedback on the Commands page).

Content indexer

Mon, 01 Jan 0001 00:00:00 +0000

Runs in: GitHub Actions (bot-index-content.yml, Ubuntu runner) executing Node.js code in indexer/, which calls Cloudflare Workers AI for embeddings and Cloudflare Vectorize to store them. The answers Jinx gives in DMs and the Assistant panel come from a Cloudflare Vectorize index called rladies-content. A separate weekly workflow walks a set of sources, chunks them, embeds each chunk with the BGE model, and upserts the vectors into the index. The same index is queried at retrieval time from the worker.

Airtable invite webhook

Mon, 01 Jan 0001 00:00:00 +0000

Runs in: Cloudflare Worker (worker/src/airtable-invite.js). No GitHub Actions, no R package. When someone fills the RLadies+ chapter sign-up form (an Airtable form), Airtable POSTs a webhook to the Cloudflare Worker. The worker validates the request, checks the source base is on a per-token allowlist, and posts an actionable message in #new-invitee with an Invite button. An organiser clicks the button, the worker invites the email to the community Slack workspace, and updates the Airtable record so it does not re-fire.

For developers

Mon, 01 Jan 0001 00:00:00 +0000

This page is for the org members who write workflows or hack on Jinx itself. If you just want to know what /jinx can do, Commands is the place. For a quick map of which code runs in which runtime, see “Where the code runs” on the landing page. Under the hood A workflow that wants to act as Jinx follows a three-step pattern.

Troubleshooting

Mon, 01 Jan 0001 00:00:00 +0000

A few failure modes that have actually happened. GitHub Actions “A JSON web token could not be decoded” – the private key in JINX_PRIVATE_KEY is not a valid PEM. This usually means the contents were truncated when pasted, or a repo-level secret is shadowing the org-level one. Check gh secret list --repo rladies/ for repo-level overrides and delete them if they exist.