website-and-documentation/content/en/docs/components/forgejo.md
Stephan Lo 82d424aeca fix(docs): remove Backstage component and add editorial headers
- Remove Backstage component page (not in product structure)
- Add editorial status alert to all draft pages with:
  * Jira ticket reference placeholder
  * Assignee field
  * Draft status indicator
  * Last updated date
  * TODO checklist for completion
- Update component template with editorial header
- Use Docsy alert shortcode (warning style) for professional appearance
2025-11-16 13:42:58 +01:00

1.8 KiB

title linkTitle weight description
Forgejo Forgejo 1 Self-hosted Git service with repository management and collaboration features.

{{% alert title="Draft" color="warning" %}} Editorial Status: This page is currently being developed.

  • Jira Ticket: TBD
  • Assignee: Team
  • Status: Draft - Template populated
  • Last Updated: 2025-11-16
  • TODO:
    • Add deployment details and access information
    • Include usage examples and workflows
    • Add screenshots
    • Document integration with Woodpecker CI {{% /alert %}}

Overview

Forgejo is a self-hosted Git service that provides repository management, issue tracking, pull requests, and collaboration features. It serves as a core component of the EDP for source code management.

Key Features

  • Git repository hosting
  • Issue tracking and project management
  • Pull requests and code review
  • CI/CD integration with Woodpecker
  • User and organization management
  • API for automation and integration

Purpose in EDP

Forgejo serves as the primary source code management platform, providing developers with a familiar Git workflow while maintaining full control over the hosting infrastructure.

Repository

Code: [Link to Forgejo repository]

Documentation: [Link to Forgejo-specific documentation]

Getting Started

[To be documented: Quick start guide for using Forgejo in EDP]

Integration Points

  • Woodpecker CI: Automated pipeline triggers on git events
  • ArgoCD: GitOps repository source
  • Backstage: Service catalog integration

Status

Maturity: Production

Documentation Notes

This is a template page. Team members should fill in:

  • Specific deployment details
  • Access URLs and credentials management
  • Common workflows and usage patterns
  • Troubleshooting information
  • Screenshots or examples