DEDUPED Hot AI repos, turned into use cases Get the Monday 5

How to link pull requests to issues and move them on merge with Itsaplan

Write Fixes KEY-42 in a pull request so the issue follows the code through review.

Who it is forA developer or tech lead whose team tracks work in It's a Plan but ships code on GitHub, GitLab, Gitea, Forgejo, or Bitbucket.

The problemIssues go stale after the code is merged because nobody updates the tracker by hand.

The outcomeThe pull request is linked to the issue, and the issue moves when the pull request opens and merges.

What you need first

  • Docker and Bun for a local try-out, or a Railway account with a domain of your own for hosted deploy
  • A model or coding CLI for internal or external agents, if you use agents
  • Admin access to the instance to set up agents and API keys

Steps

  1. Connect your repository's forge to the instance, using GitHub, GitLab, Gitea, Forgejo, or Bitbucket.
  2. Find the issue key on the board, for example KEY-42.
  3. Write "Fixes KEY-42" in the pull request title or description.
  4. Open the pull request and check that it appears on the linked issue.
  5. Merge the pull request and confirm the issue moved to the state you expect.

Prompt for your agent

For the itsaplan issue <issue key>, open a pull request in <repo> whose description says "Fixes <issue key>". Report whether the pull request is linked to the issue and whether the issue state changes after the pull request opens and after it merges.

Caveat. The README gives the "Fixes KEY-42" pattern as an example only, so test it on one pull request before relying on it across the team.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page