github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-25 07:56:03 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Feature Request: AI-Powered Code Agent for Gitea #14521

New Issue
Closed
opened 2025-11-02 11:15:09 -06:00 by GiteaMirror · 4 comments
GiteaMirror commented 2025-11-02 11:15:09 -06:00
Owner
Copy Link

Originally created by @ga-it on GitHub (May 23, 2025).

Feature Description

Summary

Implement an AI-powered code agent for Gitea that provides interactive code assistance, automated code reviews, and autonomous code implementation capabilities directly within pull requests and issues. This implementation would leverage the open-source OpenAI Codex CLI as a foundation, adapting its proven architecture for seamless Gitea integration.

Problem Statement

Currently, Gitea users lack an integrated AI assistant that can:

  • Automatically review code changes and suggest improvements
  • Answer questions about code architecture and implementation
  • Implement code fixes and features based on natural language requests
  • Provide interactive assistance during the development workflow
  • Autonomously handle complex, multi-file coding tasks (Jules-inspired)
  • Generate entire functions and applications from natural language (Codex-inspired)
  • Integrate with development workflows beyond just PR/issue comments

This feature gap makes it harder for teams to leverage AI capabilities for code quality improvement, faster development cycles, and automated code reviews, especially for open-source projects and smaller teams that rely on Gitea.

Proposed Solution

Implementation Strategy: Fork and Adapt OpenAI Codex CLI

We propose forking the OpenAI Codex CLI as the foundation for Gitea's AI assistant. This approach offers several advantages:

  1. Proven Architecture: Codex CLI already implements robust sandboxing, multi-provider support, and chat-driven development
  2. Security-First Design: Built-in approval modes, sandboxed execution, and network isolation
  3. Extensible Provider System: Supports 10+ AI providers out of the box with easy addition of new ones
  4. Active Development: Benefits from OpenAI's ongoing improvements and community contributions
  5. Open Source: Apache-2.0 licensed, allowing for modification and redistribution

Adaptation Plan

  1. Core Integration Module (gitea-codex-bridge)

    • Adapt Codex CLI's terminal interface to work with Gitea's API
    • Create webhook handlers for Gitea events
    • Implement comment parsing and response formatting for Gitea's UI

  2. Gitea Actions Wrapper

    • Create Gitea Actions that invoke the adapted Codex CLI
    • Handle authentication and secret management
    • Manage long-running tasks and status updates

  3. Enhanced Features for Gitea

    • Add Gitea-specific tools (PR management, issue handling, etc.)
    • Integrate with Gitea's permission system
    • Support for Gitea's unique features (e.g., repository templates, organizations)

Core Features (Building on Codex CLI)

  1. Interactive Code Assistant (Codex CLI Foundation)

    • Leverages Codex's existing REPL and chat interface
    • Adapts terminal interaction to PR/issue comments
    • Maintains Codex's context awareness with AGENTS.md files
    • Natural language to code translation using Codex's generation capabilities

  2. Automated Code Review (Enhanced)

    • Extends Codex's code analysis capabilities
    • Integrates with Gitea's PR review system
    • Uses Codex's multi-file understanding for comprehensive reviews
    • Leverages existing security scanning capabilities

  3. Autonomous Code Implementation (Codex CLI + Jules concepts)

    • Uses Codex's existing approval modes (suggest/auto-edit/full-auto)
    • Extends with Jules-like persistent task management
    • Leverages Codex's sandboxed execution environment
    • Builds on Codex's file manipulation and testing capabilities

  4. Advanced Code Generation (Native Codex Features)

    • Direct use of Codex's code generation capabilities
    • Existing support for test generation and refactoring
    • Multi-language support through provider flexibility
    • SQL query generation and API client creation

  5. Security and Sandboxing (Codex CLI's Robust Model)

    • Adopts Codex's platform-specific sandboxing (Seatbelt on macOS, Docker on Linux)
    • Network isolation with configurable exceptions
    • Approval workflows with three-tier permission model
    • Repository-scoped execution limits

Technical Architecture

  1. Gitea Actions Integration

    name: Gitea AI Assistant (Powered by Codex)
on:
  issue_comment:
    types: [created]
  pull_request_comment:
    types: [created]
  pull_request:
    types: [opened, synchronize]

jobs:
  ai-response:
    runs-on: ubuntu-latest
    steps:
      - uses: gitea/setup-codex-action@v1
        with:
          # Install and configure the Gitea-adapted Codex CLI
          version: "latest"

      - uses: gitea/codex-bridge-action@v1
        with:
          # Codex CLI configuration (inherited)
          provider: ${{ vars.AI_PROVIDER || 'openai' }}
          model: ${{ vars.AI_MODEL || 'gpt-4' }}
          api_key: ${{ secrets.AI_API_KEY }}

          # Codex approval modes
          approval_mode: ${{ vars.APPROVAL_MODE || 'suggest' }}

          # Gitea-specific configuration
          gitea_token: ${{ secrets.GITEA_TOKEN }}
          trigger_phrase: "@ai"

          # Codex CLI features
          allowed_tools: "Edit,Replace,FileRead,CreateFile,Bash(npm test)"
          custom_instructions: |
            Follow the coding standards in CONTRIBUTING.md
            Use Gitea API for PR/issue operations

  2. Configuration Management (Codex CLI Compatible)

    • Reuse Codex's ~/.codex/config.yaml structure
    • Add Gitea-specific configuration section
    • Maintain compatibility with Codex's provider configuration
    • Support for AGENTS.md files for project-specific instructions

  3. Provider Support (Codex CLI's Extensive List)

    • All existing Codex providers (OpenAI, Anthropic, Google, Ollama, etc.)
    • Same environment variable configuration
    • Identical model selection interface
    • Easy addition of new providers

Implementation Phases

Phase 1: Core Fork and Integration (Months 1-2)

  1. Fork OpenAI Codex CLI repository
  2. Create gitea-codex-bridge module
  3. Implement basic Gitea Actions integration
  4. Adapt comment-based interactions for Gitea's UI

Phase 2: Feature Parity (Months 3-4)

  1. Full PR/issue comment support
  2. Gitea-specific tool implementations
  3. Permission system integration
  4. Status reporting and progress tracking

Phase 3: Enhanced Capabilities (Months 5-6)

  1. Long-running task support (Jules-inspired)
  2. Advanced Gitea features (templates, organizations)
  3. Custom Gitea-specific providers
  4. Web UI configuration interface

Phase 4: Ecosystem Integration (Months 7-8)

  1. Plugin system for custom tools
  2. Integration with popular Gitea apps
  3. Advanced workflow templates
  4. Community provider contributions

Key Advantages of the Codex CLI Approach

  1. Immediate Feature Set

    • Multi-provider support (10+ providers)
    • Robust sandboxing and security
    • Proven code generation capabilities
    • Active maintenance and updates

  2. Development Efficiency

    • Avoid reimplementing complex features
    • Focus on Gitea-specific integration
    • Benefit from Codex's bug fixes and improvements
    • Leverage existing documentation and examples

  3. Community Benefits

    • Contributions benefit both projects
    • Shared provider implementations
    • Cross-pollination of ideas
    • Potential for official collaboration

  4. User Experience

    • Familiar interface for Codex users
    • Consistent behavior across platforms
    • Rich configuration options
    • Proven interaction patterns

Migration and Compatibility

  1. For Existing Codex Users

    • Direct configuration reuse
    • Same provider setup
    • Familiar commands and workflows
    • Easy transition to Gitea integration

  2. For New Users

    • Comprehensive onboarding from Codex
    • Extensive documentation available
    • Active community support
    • Lower learning curve

Security Considerations (Inherited from Codex)

  1. Sandboxing (Codex's Robust Implementation)

    • Platform-specific isolation (Seatbelt, Docker)
    • Network restrictions with OpenAI-only exceptions
    • File system access controls
    • Process isolation

  2. Approval Workflows (Codex's Three-Tier System)

    • Suggest mode: Read-only by default
    • Auto-edit mode: File modifications allowed
    • Full-auto mode: Complete autonomy with sandboxing

  3. Authentication (Extended for Gitea)

    • Codex's existing API key management
    • Gitea-specific token handling
    • Repository-scoped permissions
    • Audit logging for all actions

Success Metrics

  • Reduction in PR review time (target: 40%)
  • Increase in code quality metrics
  • User adoption rate (target: 60% of active repos)
  • Community contribution to AI providers
  • Codex CLI feature adoption (target: 80% of Codex features used)
  • Cross-project contributions (target: 10+ shared improvements)

Technical Considerations

Codex CLI Integration Points

  1. Core Modifications

    • Abstract terminal interface to support Gitea comments
    • Add Gitea API client alongside existing GitHub support
    • Extend webhook handling for Gitea events
    • Adapt progress reporting for web UI

  2. Maintained Compatibility

    • Keep Codex CLI's core architecture intact
    • Ensure provider system remains unchanged
    • Preserve configuration format
    • Maintain CLI interface for local development

  3. Gitea-Specific Extensions

    • Custom tools for Gitea API operations
    • Integration with Gitea's notification system
    • Support for Gitea's unique features
    • Repository migration tools

Community Impact

This feature would:

  • Make Gitea more competitive with GitHub/GitLab
  • Attract AI-conscious developers and organizations
  • Foster innovation in open-source AI tooling
  • Provide a privacy-focused alternative to proprietary solutions
  • Create synergy between Codex and Gitea communities
  • Accelerate AI assistant adoption through proven technology
  • Enable smaller teams to leverage enterprise-grade AI tools

References

Conclusion

By building on the OpenAI Codex CLI's proven foundation, Gitea can rapidly implement a world-class AI assistant while maintaining its commitment to open-source values and self-hosted deployments. This approach minimizes development risk, accelerates time-to-market, and ensures compatibility with the broader AI development ecosystem.

The Codex CLI's architecture, with its robust sandboxing, multi-provider support, and extensible design, provides exactly the foundation needed for a production-ready Gitea AI assistant. Rather than reinventing the wheel, we can focus on creating the best possible integration with Gitea's unique features and workflows.

Note: This proposal leverages the OpenAI Codex CLI's mature architecture while adding Gitea-specific enhancements. The implementation would maintain compatibility with Codex's ecosystem while providing a seamless experience for Gitea users. The Apache-2.0 license of Codex CLI allows for this adaptation while contributing improvements back to the original project.

Originally created by @ga-it on GitHub (May 23, 2025). ### Feature Description ## Summary Implement an AI-powered code agent for Gitea that provides interactive code assistance, automated code reviews, and autonomous code implementation capabilities directly within pull requests and issues. This implementation would leverage the open-source OpenAI Codex CLI as a foundation, adapting its proven architecture for seamless Gitea integration. ## Problem Statement Currently, Gitea users lack an integrated AI assistant that can: - Automatically review code changes and suggest improvements - Answer questions about code architecture and implementation - Implement code fixes and features based on natural language requests - Provide interactive assistance during the development workflow - **Autonomously handle complex, multi-file coding tasks** (Jules-inspired) - **Generate entire functions and applications from natural language** (Codex-inspired) - **Integrate with development workflows beyond just PR/issue comments** This feature gap makes it harder for teams to leverage AI capabilities for code quality improvement, faster development cycles, and automated code reviews, especially for open-source projects and smaller teams that rely on Gitea. ## Proposed Solution ### Implementation Strategy: Fork and Adapt OpenAI Codex CLI We propose forking the [OpenAI Codex CLI](https://github.com/openai/codex) as the foundation for Gitea's AI assistant. This approach offers several advantages: 1. **Proven Architecture**: Codex CLI already implements robust sandboxing, multi-provider support, and chat-driven development 2. **Security-First Design**: Built-in approval modes, sandboxed execution, and network isolation 3. **Extensible Provider System**: Supports 10+ AI providers out of the box with easy addition of new ones 4. **Active Development**: Benefits from OpenAI's ongoing improvements and community contributions 5. **Open Source**: Apache-2.0 licensed, allowing for modification and redistribution #### Adaptation Plan 1. **Core Integration Module** (`gitea-codex-bridge`) - Adapt Codex CLI's terminal interface to work with Gitea's API - Create webhook handlers for Gitea events - Implement comment parsing and response formatting for Gitea's UI 2. **Gitea Actions Wrapper** - Create Gitea Actions that invoke the adapted Codex CLI - Handle authentication and secret management - Manage long-running tasks and status updates 3. **Enhanced Features for Gitea** - Add Gitea-specific tools (PR management, issue handling, etc.) - Integrate with Gitea's permission system - Support for Gitea's unique features (e.g., repository templates, organizations) ### Core Features (Building on Codex CLI) 1. **Interactive Code Assistant** (Codex CLI Foundation) - Leverages Codex's existing REPL and chat interface - Adapts terminal interaction to PR/issue comments - Maintains Codex's context awareness with `AGENTS.md` files - Natural language to code translation using Codex's generation capabilities 2. **Automated Code Review** (Enhanced) - Extends Codex's code analysis capabilities - Integrates with Gitea's PR review system - Uses Codex's multi-file understanding for comprehensive reviews - Leverages existing security scanning capabilities 3. **Autonomous Code Implementation** (Codex CLI + Jules concepts) - Uses Codex's existing approval modes (suggest/auto-edit/full-auto) - Extends with Jules-like persistent task management - Leverages Codex's sandboxed execution environment - Builds on Codex's file manipulation and testing capabilities 4. **Advanced Code Generation** (Native Codex Features) - Direct use of Codex's code generation capabilities - Existing support for test generation and refactoring - Multi-language support through provider flexibility - SQL query generation and API client creation 5. **Security and Sandboxing** (Codex CLI's Robust Model) - Adopts Codex's platform-specific sandboxing (Seatbelt on macOS, Docker on Linux) - Network isolation with configurable exceptions - Approval workflows with three-tier permission model - Repository-scoped execution limits ### Technical Architecture 1. **Gitea Actions Integration** ```yaml name: Gitea AI Assistant (Powered by Codex) on: issue_comment: types: [created] pull_request_comment: types: [created] pull_request: types: [opened, synchronize] jobs: ai-response: runs-on: ubuntu-latest steps: - uses: gitea/setup-codex-action@v1 with: # Install and configure the Gitea-adapted Codex CLI version: "latest" - uses: gitea/codex-bridge-action@v1 with: # Codex CLI configuration (inherited) provider: ${{ vars.AI_PROVIDER || 'openai' }} model: ${{ vars.AI_MODEL || 'gpt-4' }} api_key: ${{ secrets.AI_API_KEY }} # Codex approval modes approval_mode: ${{ vars.APPROVAL_MODE || 'suggest' }} # Gitea-specific configuration gitea_token: ${{ secrets.GITEA_TOKEN }} trigger_phrase: "@ai" # Codex CLI features allowed_tools: "Edit,Replace,FileRead,CreateFile,Bash(npm test)" custom_instructions: | Follow the coding standards in CONTRIBUTING.md Use Gitea API for PR/issue operations ``` 2. **Configuration Management** (Codex CLI Compatible) - Reuse Codex's `~/.codex/config.yaml` structure - Add Gitea-specific configuration section - Maintain compatibility with Codex's provider configuration - Support for `AGENTS.md` files for project-specific instructions 3. **Provider Support** (Codex CLI's Extensive List) - All existing Codex providers (OpenAI, Anthropic, Google, Ollama, etc.) - Same environment variable configuration - Identical model selection interface - Easy addition of new providers ### Implementation Phases #### Phase 1: Core Fork and Integration (Months 1-2) 1. Fork OpenAI Codex CLI repository 2. Create `gitea-codex-bridge` module 3. Implement basic Gitea Actions integration 4. Adapt comment-based interactions for Gitea's UI #### Phase 2: Feature Parity (Months 3-4) 1. Full PR/issue comment support 2. Gitea-specific tool implementations 3. Permission system integration 4. Status reporting and progress tracking #### Phase 3: Enhanced Capabilities (Months 5-6) 1. Long-running task support (Jules-inspired) 2. Advanced Gitea features (templates, organizations) 3. Custom Gitea-specific providers 4. Web UI configuration interface #### Phase 4: Ecosystem Integration (Months 7-8) 1. Plugin system for custom tools 2. Integration with popular Gitea apps 3. Advanced workflow templates 4. Community provider contributions ### Key Advantages of the Codex CLI Approach 1. **Immediate Feature Set** - Multi-provider support (10+ providers) - Robust sandboxing and security - Proven code generation capabilities - Active maintenance and updates 2. **Development Efficiency** - Avoid reimplementing complex features - Focus on Gitea-specific integration - Benefit from Codex's bug fixes and improvements - Leverage existing documentation and examples 3. **Community Benefits** - Contributions benefit both projects - Shared provider implementations - Cross-pollination of ideas - Potential for official collaboration 4. **User Experience** - Familiar interface for Codex users - Consistent behavior across platforms - Rich configuration options - Proven interaction patterns ### Migration and Compatibility 1. **For Existing Codex Users** - Direct configuration reuse - Same provider setup - Familiar commands and workflows - Easy transition to Gitea integration 2. **For New Users** - Comprehensive onboarding from Codex - Extensive documentation available - Active community support - Lower learning curve ### Security Considerations (Inherited from Codex) 1. **Sandboxing** (Codex's Robust Implementation) - Platform-specific isolation (Seatbelt, Docker) - Network restrictions with OpenAI-only exceptions - File system access controls - Process isolation 2. **Approval Workflows** (Codex's Three-Tier System) - Suggest mode: Read-only by default - Auto-edit mode: File modifications allowed - Full-auto mode: Complete autonomy with sandboxing 3. **Authentication** (Extended for Gitea) - Codex's existing API key management - Gitea-specific token handling - Repository-scoped permissions - Audit logging for all actions ## Success Metrics - Reduction in PR review time (target: 40%) - Increase in code quality metrics - User adoption rate (target: 60% of active repos) - Community contribution to AI providers - **Codex CLI feature adoption** (target: 80% of Codex features used) - **Cross-project contributions** (target: 10+ shared improvements) ## Technical Considerations ### Codex CLI Integration Points 1. **Core Modifications** - Abstract terminal interface to support Gitea comments - Add Gitea API client alongside existing GitHub support - Extend webhook handling for Gitea events - Adapt progress reporting for web UI 2. **Maintained Compatibility** - Keep Codex CLI's core architecture intact - Ensure provider system remains unchanged - Preserve configuration format - Maintain CLI interface for local development 3. **Gitea-Specific Extensions** - Custom tools for Gitea API operations - Integration with Gitea's notification system - Support for Gitea's unique features - Repository migration tools ## Community Impact This feature would: - Make Gitea more competitive with GitHub/GitLab - Attract AI-conscious developers and organizations - Foster innovation in open-source AI tooling - Provide a privacy-focused alternative to proprietary solutions - **Create synergy between Codex and Gitea communities** - **Accelerate AI assistant adoption through proven technology** - **Enable smaller teams to leverage enterprise-grade AI tools** ## References - [OpenAI Codex CLI](https://github.com/openai/codex) - Foundation for implementation - [GitHub Claude Code Action](https://github.com/anthropics/claude-code-action) - [Google Jules](https://blog.google/technology/google-labs/jules/) - [OpenAI Codex Introduction](https://openai.com/index/introducing-codex/) - [Gitea Actions Documentation](https://docs.gitea.com/usage/actions/overview) ## Conclusion By building on the OpenAI Codex CLI's proven foundation, Gitea can rapidly implement a world-class AI assistant while maintaining its commitment to open-source values and self-hosted deployments. This approach minimizes development risk, accelerates time-to-market, and ensures compatibility with the broader AI development ecosystem. The Codex CLI's architecture, with its robust sandboxing, multi-provider support, and extensible design, provides exactly the foundation needed for a production-ready Gitea AI assistant. Rather than reinventing the wheel, we can focus on creating the best possible integration with Gitea's unique features and workflows. --- **Note**: This proposal leverages the OpenAI Codex CLI's mature architecture while adding Gitea-specific enhancements. The implementation would maintain compatibility with Codex's ecosystem while providing a seamless experience for Gitea users. The Apache-2.0 license of Codex CLI allows for this adaptation while contributing improvements back to the original project.
GiteaMirror added the type/proposal label 2025-11-02 11:15:09 -06:00
GiteaMirror commented 2025-11-02 11:15:10 -06:00
Author
Owner
Copy Link

@techknowlogick commented on GitHub (May 23, 2025):

Thank you for this issue. I'm hesitant to build this directly into the app, for many reasons, but one of the primary ones is once something is merged, it requires continued maintenance. Regardless, it sounds like this can be done without any changes to Gitea itself, as action workflows aren't directly inside of the gitea repo, and a fork of codex would still be outside of this repo. With that in mind, I would recommend that you could fork codex and add in the integration with the Gitea API (there is an MCP provider already), and create an action to listen for events to trigger the workflow, and then that way it would achieve your preferred end goal.

@techknowlogick commented on GitHub (May 23, 2025): Thank you for this issue. I'm hesitant to build this directly into the app, for many reasons, but one of the primary ones is once something is merged, it requires continued maintenance. Regardless, it sounds like this can be done without any changes to Gitea itself, as action workflows aren't directly inside of the gitea repo, and a fork of codex would still be outside of this repo. With that in mind, I would recommend that you could fork codex and add in the integration with the Gitea API (there is an MCP provider already), and create an action to listen for events to trigger the workflow, and then that way it would achieve your preferred end goal.
GiteaMirror commented 2025-11-02 11:15:10 -06:00
Author
Owner
Copy Link

@ga-it commented on GitHub (May 23, 2025):

Hi @techknowlogick

Thanks for all the amazing work you guys do and the awesome Gitea.

I completely understand being cautious of including new functionality into the Gitea core given maintenance requirements.

However, I think we are in a "moment" - Github spoke at "Code with Claude* yesterday and unveiled an entire new agentic coding architecture for github:

Image

https://www.youtube.com/live/EvtPBaaykdo?si=5sGlKwtRkBlB1Vwv

This takes Copilot and provides front end integration for triggering and showing agent actions.

Codex, Jules and Claude 4 have all announced github integration in the last week.

If you are of the school that believes AI agents will act as developers in the future, then it would seem to make sense that capability to manage this be placed front and Centre in the GUI.

The Claude with Code excalidraw demo was jaw dropping.

I agree it can work via api, MCP and in the background and maybe that is the place to start. But I do think this is a seismic shift that Gitea would be even better for embracing.

@ga-it commented on GitHub (May 23, 2025): Hi @techknowlogick Thanks for all the amazing work you guys do and the awesome Gitea. I completely understand being cautious of including new functionality into the Gitea core given maintenance requirements. However, I think we are in a "moment" - Github spoke at "Code with Claude* yesterday and unveiled an entire new agentic coding architecture for github: ![Image](https://github.com/user-attachments/assets/bc01fa68-58d8-47ec-ad15-5f4e059e88e0) https://www.youtube.com/live/EvtPBaaykdo?si=5sGlKwtRkBlB1Vwv This takes Copilot and provides front end integration for triggering and showing agent actions. Codex, Jules and Claude 4 have all announced github integration in the last week. If you are of the school that believes AI agents will act as developers in the future, then it would seem to make sense that capability to manage this be placed front and Centre in the GUI. The Claude with Code excalidraw demo was jaw dropping. I agree it can work via api, MCP and in the background and maybe that is the place to start. But I do think this is a seismic shift that Gitea would be even better for embracing.
GiteaMirror commented 2025-11-02 11:15:10 -06:00
Author
Owner
Copy Link

@TheFox0x7 commented on GitHub (May 23, 2025):

I'm against implementing any of that in Gitea at the moment. There already are people that are annoyed by github constant pushing of copilot everywhere hoping it might stick. Quite frankly I don't find github's built-in copilot integration as something worth mirroring.
Let's leave this to third party tools. I'd much rather add something to the Gitea instance separately and let it skim through my code than have an instance wide integration do whatever it wants. It's also less lock-in.

Did you generate the original feature request using LLMs? Because it sounds like it to me.

@TheFox0x7 commented on GitHub (May 23, 2025): I'm against implementing any of that in Gitea at the moment. There already are people that are annoyed by github constant pushing of copilot everywhere hoping it might stick. Quite frankly I don't find github's built-in copilot integration as something worth mirroring. Let's leave this to third party tools. I'd much rather add something to the Gitea instance separately and let it skim through my code than have an instance wide integration do whatever it wants. It's also less lock-in. Did you generate the original feature request using LLMs? Because it sounds like it to me.
GiteaMirror commented 2025-11-02 11:15:11 -06:00
Author
Owner
Copy Link

@ga-it commented on GitHub (May 23, 2025):

@TheFox0x7 never mind. Your last paragraph said enough

@ga-it commented on GitHub (May 23, 2025): @TheFox0x7 never mind. Your last paragraph said enough
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label type/proposal
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#14521
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?