DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to trigger a deploy or mirror after each successful push with Enroute

Use a post-receive hook to start CI, deploy code or mirror a repo after a push lands.

Who it is forA developer who wants every successful push to kick off a build, a deploy or a copy to another repository.

The problemWiring Git pushes to CI or deployment often means polling or extra services that have to be kept in sync.

The outcomeA post-receive handler that runs your chosen action each time a push succeeds.

What you need first

  • Linux or macOS on Apple silicon, or Docker to run the published image
  • git installed on your machine
  • A terminal and, for hooks, a language you can write a small server in

Steps

  1. Read the post-receive section in docs/reference/hooks.md for the payload it receives.
  2. Write a post-receive handler in your app that starts your CI run, deploy script or mirror job.
  3. Enable the post-receive hook following the setup in docs/README.md. (inferred, check the README)
  4. Push a commit with git push http://127.0.0.1:8080/hello.git main and check that your action ran. (inferred, check the README)

Prompt for your agent

In the enroute-sh/enroute repository, read docs/reference/hooks.md and write a post-receive handler in <app-dir> that starts a deploy script for <repo-name>. Expected output: the handler runs after a successful push. Verify by pushing a commit to main and checking the deploy script log.

Caveat. The README lists post-receive as a hook for running CI, deploys or mirroring, but it does not describe the deploy or mirror tooling, so you supply that yourself.

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