opencommit/roadmap

Release Drafter for Forgejo (Action) #4

New issue

Open

opened 2026-04-11 22:00:59 +02:00 by mvdkleijn · 0 comments

mvdkleijn commented

2026-04-11 22:00:59 +02:00

Owner

1. What

Development of a high-fidelity, drop-in replacement for the widely used Release Drafter action on Github, specifically optimized for the Forgejo/OpenCommit ecosystem. The goal is to provide a seamless migration path for developers moving workflows from GitHub to OpenCommit by maintaining near-perfect compatibility with existing YAML configurations and release-drafting logic.

2. Why

Frictionless Migration: Lowers the barrier to entry for GitHub users by allowing them to port their existing CI/CD pipelines to OpenCommit without rewriting workflow logic.
Ecosystem Maturity: Instantly provides a professional-grade, battle-tested automation capability that mirrors a widely used action on Github.
Developer Velocity: Enables developers to leverage familiar configuration patterns, reducing the learning curve and accelerating their adoption of the OpenCommit platform.

3. Boundaries

In-Scope:
- Configuration Parity: Supporting the same release-drafter.yml structures used by the original GitHub action.
- Logic Emulation: Replicating the parsing of files patterns, PR labels, commit messages, and tag patterns to generate consistent release notes.
- Forgejo Integration: Use of the "Draft Release" API calls to work specifically with Forgejo’s repository architecture.
- Workflow Compatibility: Ensuring the action is triggerable via standard workflow_dispatch and push events in Forgejo Actions.
Out-of-Scope:
- Adding new, non-standard features that deviate from the original action's logic (to avoid breaking existing user patterns).
  **Support for GitHub-specific proprietary APIs that do not exist in the Forgejo/Git ecosystem.

4. Definition of Done

Configuration Compatibility: A standard release-drafter.yml used in a GitHub workflow can be used in an OpenCommit workflow with zero to minimal modification.
Logic Parity: The generated release notes (structure, content, and parsing accuracy) are near indistinguishable from the original action's output.
Seamless Integration: The action successfully interacts with the Forgejo API to create/update drafts without requiring custom authentication setup by the user.
Regression Testing: Automated tests confirm that common configuration patterns (e.g., regex for labels, template overrides) behave identically to the reference implementation.
Performance: The action executes within a reasonable time frame, ensuring it does not bottleneck the continuous integration pipeline.

## **1. What** Development of a high-fidelity, drop-in replacement for the widely used Release Drafter action on Github, specifically optimized for the Forgejo/OpenCommit ecosystem. The goal is to provide a seamless migration path for developers moving workflows from GitHub to OpenCommit by maintaining near-perfect compatibility with existing YAML configurations and release-drafting logic. ## **2. Why** * **Frictionless Migration:** Lowers the barrier to entry for GitHub users by allowing them to port their existing CI/CD pipelines to OpenCommit without rewriting workflow logic. * **Ecosystem Maturity:** Instantly provides a professional-grade, battle-tested automation capability that mirrors a widely used action on Github. * **Developer Velocity:** Enables developers to leverage familiar configuration patterns, reducing the learning curve and accelerating their adoption of the OpenCommit platform. ## **3. Boundaries** * **In-Scope:** * **Configuration Parity:** Supporting the same `release-drafter.yml` structures used by the original GitHub action. * **Logic Emulation:** Replicating the parsing of files patterns, PR labels, commit messages, and tag patterns to generate consistent release notes. * **Forgejo Integration:** Use of the "Draft Release" API calls to work specifically with Forgejo’s repository architecture. * **Workflow Compatibility:** Ensuring the action is triggerable via standard `workflow_dispatch` and `push` events in Forgejo Actions. * **Out-of-Scope:** * Adding new, non-standard features that deviate from the original action's logic (to avoid breaking existing user patterns). **Support for GitHub-specific proprietary APIs that do not exist in the Forgejo/Git ecosystem. ## **4. Definition of Done** * [ ] **Configuration Compatibility:** A standard `release-drafter.yml` used in a GitHub workflow can be used in an OpenCommit workflow with zero to minimal modification. * [ ] **Logic Parity:** The generated release notes (structure, content, and parsing accuracy) are near indistinguishable from the original action's output. * [ ] **Seamless Integration:** The action successfully interacts with the Forgejo API to create/update drafts without requiring custom authentication setup by the user. * [ ] **Regression Testing:** Automated tests confirm that common configuration patterns (e.g., regex for labels, template overrides) behave identically to the reference implementation. * [ ] **Performance:** The action executes within a reasonable time frame, ensuring it does not bottleneck the continuous integration pipeline.