# Integration with source control / GitHub / GitLab / Forgejo

**URL:** <https://community.vikunja.io/t/integration-with-source-control-github-gitlab-forgejo/4738>\
**Category:** Feature Discussion\
**Created:** [6 August 2026 17:06 UTC](https://community.vikunja.io/t/integration-with-source-control-github-gitlab-forgejo/4738 "2026-08-06T17:06:34Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![calmh](https://community.vikunja.io/user_avatar/community.vikunja.io/calmh/32/2873_2.png) [@calmh](https://community.vikunja.io/u/calmh)\
**Post date:** [6 August 2026 17:06 UTC](https://community.vikunja.io/t/integration-with-source-control-github-gitlab-forgejo/4738/1 "2026-08-06T17:06:34Z")

</div>

I’m wondering what possibilities there are for integrating with any code forge, such that pull requests and commits can drive issue statuses via `fixes #1234` and similar annotations in the commit / PR body.

---

<div class="post-metadata">

**Author:** ![malys](https://community.vikunja.io/user_avatar/community.vikunja.io/malys/32/2457_2.png) [@malys](https://community.vikunja.io/u/malys)\
**Post date:** [9 August 2026 08:28 UTC](https://community.vikunja.io/t/integration-with-source-control-github-gitlab-forgejo/4738/2 "2026-08-09T08:28:29Z")

</div>

Feegejo webhook to vikunja api???

---

<div class="post-metadata">

**Author:** ![calmh](https://community.vikunja.io/user_avatar/community.vikunja.io/calmh/32/2873_2.png) [@calmh](https://community.vikunja.io/u/calmh)\
**Post date:** [28 August 2026 09:16 UTC](https://community.vikunja.io/t/integration-with-source-control-github-gitlab-forgejo/4738/3 "2026-08-28T09:16:18Z")

</div>

Yeah… I guess with Vikunja itself using the GitHub issue tracker for its development, this is not one of the priorities. 😉
