Skip to content

Conversation

@tdruez
Copy link
Contributor

@tdruez tdruez commented Aug 7, 2025

Issue: #347

Notes

Forgejo is a self-hosted lightweight software forge. Easy to install and low maintenance, it just does the job.

Although Forgejo is meant to be self-hosted, a testing platform is available at https://v12.next.forgejo.org/ ("Try now" link on the https://forgejo.org/ homepage).

The testing Forgero platform is working fine to test and review this integration. Use the "Register" link and create an account.

Documentation

https://dejacode.readthedocs.io/en/latest/integrations-forgejo.html

Changes

  • Add a forgejo_token field on the Dataspace configuration model.
  • The integration code exists as the ForgejoIntegration class.
  • Add a base_url field on the ExternalIssueLink model to support dynamic domains (Forgejo, Jira, ...)

Quickstart

Prerequisites

  • A Forgejo repo that you want to integrate with DejaCode.
  • A Forgejo user account with sufficient permissions to create and manage issues in the target repo.

DejaCode configuration

  1. Set your forgejo_token on your Dataspace configuration.
  2. Create a new RequestTemplate in your Dataspace and use your Forgejo project URL as the Issue Tracker ID, e.g.: https://forgejo.example.org/org/repo_name
  3. From now on, any new DejaCode Request using this template will be pushed to the Forgejo-provided repo. Edits such as field updates, comments, and closing the Request are also propagated to the Forgejo Issue.

Refer to https://dejacode.readthedocs.io/en/latest/integrations-forgejo.html for detailed instructions.

@DennisClark
Copy link
Member

@DennisClark
Copy link
Member

DennisClark commented Aug 7, 2025

Update testing is good also. Closed the Request in DejaCode with a Comment and both the Status update and Comment insert were successful in Forgejo.

@tdruez No problems found! The configuration documentation was clear enough and sufficient for me to do the setup. Let me know if you want me to do any more testing.

@tdruez tdruez merged commit 768c609 into main Aug 8, 2025
4 checks passed
@tdruez tdruez deleted the 347-forgejo-integration branch August 8, 2025 08:06
@tdruez tdruez changed the title Add Forgejo workflow Request integration #350 CRAVEX Forgejo workflow Request integration Aug 11, 2025
@tdruez tdruez changed the title CRAVEX Forgejo workflow Request integration CRAVEX Forgejo workflow integration Aug 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants