Asana has its own GitHub app, and for a team that lives entirely in GitHub it can be enough: it links pull requests and branches to tasks and can move a task along when a pull request merges. Two things it does not do. It has no Bitbucket equivalent, and what it reports on the task is the pull request and the branch rather than the commits behind them. Astogi covers that narrower gap. Put a task number such as ABC-0042 in a commit message on GitHub or Bitbucket, push, and the commit appears as a comment on that Asana task, with the author, the commit message and a link back to the commit. No pull request has to exist, and nobody has to paste a task link into a branch name. The number is the part that makes it work in practice. Astogi's task numbering writes it into the task name itself, so ABC-0042 is short enough to type from memory, it reads cleanly in a git log, and it is the same reference people already use in standups and email subjects. The comment on the task closes the loop for everyone who does not read the repository.
Connecting a repository is a dashboard step, not a repository settings chore. In the Repositories section you authorise GitHub or Bitbucket, pick the repository, and link it to the Asana project or projects it belongs to. Astogi then registers a push webhook on the repository with the access you granted, which is why it asks for permission to manage webhooks. It reads the payload of a push and never your source code. When someone pushes, the payload is stored and a queued job picks it up. It reads the head commit of that push: the author's name, the commit message and the link to the commit on GitHub or Bitbucket. Then, for every Asana project linked to that repository, it compares each task's number against that message. The match is plain text anywhere in the message, so a prefix, a trailer or a line in the body all work. Two details stop false matches. A number only counts when the character after it is not a digit, so ABC-4 never matches ABC-42. And padding is part of the string: if your project pads to four digits, ABC-42 and ABC-0042 are different, and only the padded one matches. Copying the number out of the task name avoids both problems. One comment is posted per push, built from the head commit, rather than one comment per commit. A push of six commits gives the task one readable update, which also means the number has to be in the message of the last commit in the push for that push to be picked up. Put it on the final commit, or on all of them. The comment goes in through the Asana API as the Astogi user that numbering already added to the project, with the project's own connected user as a fallback if that fails. That is why removing the Astogi user from a project quietly stops the comments. Nothing is installed on anyone's machine and there is no per-developer setup: the only thing a developer has to know is to type the number. Branch names do not matter, so work in progress on a feature branch reaches the task the same way a commit on main does. Squash merges are the one case to watch, because the squash commit message is what lands and what gets read. If the number was only in the individual commits, put it in the pull request title, since GitHub seeds the squash message from the title by default.
Astogi supports GitHub and Bitbucket today.
GitLab is not supported out of the box yet. If you need Asana and GitLab connected, tell us on the custom integration page and we can build it for your workflow.
It matches the task number in your commit message, which works best alongside the auto numbering integration.
You can try Astogi for free on your first project. Need more? Get more for just €29/month.
If you have any question or need support, feel free to contact us, our team is always happy to come up with the best solutions to your problems.
Overvoorde 49,
Amsterdam, The Netherlands
Made with ❤️ in the Netherlands
©Astogi 2026
Registered at the
Chamber of Commerce #42271509