Skip to content
Docs · Git webhooks

Board and tickets

Git webhooks

Point a GitHub or GitLab webhook at Yomenie and tickets follow their pull and merge requests: a draft to In progress, opened to Review, merged to Done.

Updated

On this page

A git webhook lets GitHub or GitLab move tickets for you. Put a ticket’s key in a branch name or a pull request title, and the ticket follows the pull request across the board. Nobody drags cards after the fact, and nobody has to remember to.

It works with GitHub, GitHub Enterprise, GitLab.com and self-hosted GitLab. There’s no app to install, and Yomenie keeps no GitHub or GitLab token.

Add one

Owners and admins can add git webhooks.

  1. Open Settings → Git and choose Add git webhook. Give it a name, like “GitLab”.
  2. Confirm it’s you if asked.
  3. Copy the URL, https://yomenie.us/hooks/git/ym_git_…. It’s shown only once.

One URL works for GitHub and GitLab alike, for as many repositories as you point at it. Anyone who has it can move tickets in your workspace, so keep it in the provider’s settings, not in a repository, and regenerate it if it leaks. On a public repository, anyone who can open a pull request (an outside contributor, a fork) can move a ticket by naming its key, so point the webhook only at repositories whose pull requests you’d let move your board.

Point GitHub or GitLab at it

GitHub: a repository’s or organisation’s Settings → Webhooks → Add webhook. Paste the URL, content type application/json, then Let me select individual events → Pull requests.

GitLab: a project’s or group’s Settings → Webhooks → Add new webhook. Paste the URL and tick Merge request events.

Name the ticket

Yomenie reads ticket keys from the branch name and the title, in any case: feat/yom-12-login-errors or “YOM-12: Show sign-in errors”. Keys in the description are left alone, and up to five tickets follow one pull request. Version numbers like vite-5.0.1 aren’t keys. Forgot the key? Add it to the title any time: the ticket is picked up on that edit. Taking a key out leaves that ticket where it is.

It doesn’t matter how the ticket got onto the board, or which board it’s on: the key decides. One webhook serves every board in the workspace.

What moves where

A ticket follows every pull or merge request that names it:

Its requests The ticket goes to
Any open for review Review
Otherwise, any draft In progress
Otherwise, any merged Done
All closed without merging Out of Review, back to In progress

Boards have their own columns, and the names above are the default board’s. On any board, Review is the first column marked review (a board with none isn’t moved when a request opens), In progress is where taking a ticket puts it (the first column after the first that isn’t review or the last), and Done is the last column.

So a ticket split over two repositories stays in Review until the last request merges. Tickets move only when something changes (a request merges, closes, reopens or changes draft, or a ticket is newly named), never on new commits or approvals, so a ticket you moved by hand stays put. Late and repeated deliveries change nothing, and a request opened before you added the webhook is picked up on its next event. The pull or merge request is attached to the ticket the first time it names it.

The ticket’s activity says “GitLab moved this to Review”: the webhook made the change, not a person. The usual notifications follow.

Tell your agents

Yomenie’s MCP server already tells connected agents (Claude Code, Codex, Cursor) to put the ticket key in the branch name. To have them also make or claim the ticket before they start, add a few lines to each repository’s AGENTS.md:

## Board tickets

Work here is tracked on the **Platform** board in Yomenie (keys `PLAT-<n>`), through the `yomenie`
MCP tools. Before creating a branch for work that will end in a pull request, claim the ticket you
were asked about, or find a match that's yours or unassigned, or create one on the Platform board
assigned to you in In progress. Name the branch `feat/plat-<n>-<slug>`. Once the pull request is
open, attach it to the ticket and comment on what changed. Work that changes no files gets no ticket.

Check a delivery

Yomenie answers every event in JSON, which GitHub and GitLab show in their delivery logs, for example GitLab !42 was merged: YOM-12 moved to Done. Events with nothing to do answer 200 with a note saying why, so GitLab never switches the webhook off over them.

Regenerate or revoke

In Settings → Git, owners and admins can regenerate a URL (the old one stops at once) or revoke a webhook for good. Everyone sees the list: name, who added it, its last event and how many tickets it moved. A connected app can list git webhooks and, with “Manage workspace settings”, revoke one; see Tools.