致谢 Gitea是什么? 安装 对比 Gitea 与其它 Git 托管工具 数据库准备 使用二进制文件安装 使用包管理器安装 使用源代码安装 在 Linux 中以 service 方式运行 注册为Windows服务 使用 Docker 安装 (rootless) 使用 Docker 安装 在 Kubernetes 中安装 Gitea 在云服务器中安装 Gitea 从旧版 从旧版 Gitea 升级 从 Gogs 升级 管理 Gitea 命令行 环境变量清单 备份与恢复 Email 设置 Git LFS 设置 HTTPS配置 设置 Fail2ban 反向代理 嵌入资源提取工具 配置说明 日志配置 邮件模板 仓库索引器 GPG 提交签名 外部渲染器 搜索引擎索引 自定义 Gitea 配置 添加法律页面 使用 - 2 - 本文档使用 书栈网 书栈网 · BookStack.CN 构建 Actions Gitea Actions 快速入门 Act Runner 与GitHub Actions的对比 Gitea Actions设计 Gitea Actions常见问题解答 软件包 软件包注册表 Cargo 软件包注册表 Chef 软件包注册表 存储 Composer 软件包注册表 Conan 软件包注册表 Conda

Star 13,400+ 2023年11月，飞致云与上海吉谛达成战略合作，获得 Gitea 企业版中国大陆地区独家代理权， 向中国数字化团队交付被广泛验证、可信赖的通用工具软件。 新一代的代码托管平台 Star 39,000+ 飞致云 上海吉谛 1 Gitea 开源项目介绍 Gitea 企业版介绍 3 Gitea 优势总结 2 代码托管平台的发展历程 阶段一 阶段二 阶段三 •单用户本地编辑； ClearCase。 集中式代码管理 •去中心化，稳定性和可用性增强； •更高效的代码协同机制； •典型产品：GitHub、GitLab、 Gitea。 分布式代码管理 基于 Git 的分布式 代码托管 具备 DevSecOps 延伸能力 Gitea 是谁？ • 2016 年 11 月 fork 自 gogs，开始独立发展； • 基于 MIT 开源协议； • 贡献者累计超过 1000 延伸能力 CI / CD 包/发布管理 依赖项扫描 百科管理 项目管理 其他能力… 合并请求 代码审查 分支管理 代码仓库 Git代码托管 核心能力 新一代的代码托管平台 Gitea 的定位 遵循典型的 Git flow 工作流程 编写代码 01 创建仓库 管理员创建仓库，分支保护策略 、合并方式等，并进行初始化 02 clone 仓库 开发人员将仓库 clone

Weblate currently supports Git (with extended support for GitHub pull requests, GitLab merge requests, Gitea pull requests, Gerrit and Subversion) and Mercurial as version control back-ends. Accessing repositories GITLAB_USERNAME, GITLAB_TOKEN, GITLAB_CREDENTIALS Gitea pull requests New in version 4.12. This just adds a thin layer atop Git using the Gitea API [https://docs.gitea.io/en- us/api-usage/] to allow pushing translation repository, while Gitea pull requests creates pull requests. You need to configure API credentials (GITEA_CREDENTIALS) in the Weblate settings to make this work. Once configured, you will see a Gitea option when

Weblate currently supports Git (with extended support for GitHub pull requests, GitLab merge requests, Gitea pull requests, Gerrit and Subversion) and Mercurial as version control back-ends. Accessing repositories GITLAB_USERNAME, GITLAB_TOKEN, GITLAB_CREDENTIALS Gitea pull requests New in version 4.12. This just adds a thin layer atop Git using the Gitea API [https://docs.gitea.io/en- us/api-usage/] to allow pushing translation repository, while Gitea pull requests creates pull requests. You need to configure API credentials (GITEA_CREDENTIALS) in the Weblate settings to make this work. Once configured, you will see a Gitea option when

Weblate currently supports Git (with extended support for GitHub pull requests, GitLab merge requests, Gitea pull requests, Gerrit and Subversion) and Mercurial as version control back-ends. Accessing repositories GITLAB_USERNAME, GITLAB_TOKEN, GITLAB_CREDENTIALS Gitea pull requests New in version 4.12. This just adds a thin layer atop Git using the Gitea API [https://docs.gitea.io/en- us/api-usage/] to allow pushing translation repository, while Gitea pull requests creates pull requests. You need to configure API credentials (GITEA_CREDENTIALS) in the Weblate settings to make this work. Once configured, you will see a Gitea option when

Weblate currently supports Git (with extended support for GitHub pull requests, GitLab merge requests, Gitea pull requests, Gerrit and Subversion) and Mercurial as version control back-ends. 1.11.1 Accessing GITLAB_USERNAME, GITLAB_TOKEN, GITLAB_CREDENTIALS 1.11.5 Gitea pull requests New in version 4.12. This just adds a thin layer atop Git using the Gitea API to allow pushing translation changes as pull requests repository, while Gitea pull requests creates pull requests. You need to configure API credentials (GITEA_CREDENTIALS) in the Weblate settings to make this work. Once configured, you will see a Gitea option when

Weblate currently supports Git (with extended support for GitHub pull requests, GitLab merge requests, Gitea pull requests, Gerrit and Subversion) and Mercurial as version control back-ends. 1.11.1 Accessing GITLAB_USERNAME, GITLAB_TOKEN, GITLAB_CREDENTIALS 1.11.5 Gitea pull requests New in version 4.12. This just adds a thin layer atop Git using the Gitea API to allow pushing translation changes as pull requests repository, while Gitea pull requests creates pull requests. You need to configure API credentials (GITEA_CREDENTIALS) in the Weblate settings to make this work. Once configured, you will see a Gitea option when

Weblate currently supports Git (with extended support for GitHub pull requests, GitLab merge requests, Gitea pull requests, Gerrit and Subversion) and Mercurial as version control back-ends. 1.11.1 Accessing GITLAB_USERNAME, GITLAB_TOKEN, GITLAB_CREDENTIALS 1.11.5 Gitea pull requests New in version 4.12. This just adds a thin layer atop Git using the Gitea API to allow pushing translation changes as pull requests repository, while Gitea pull requests creates pull requests. You need to configure API credentials (GITEA_CREDENTIALS) in the Weblate settings to make this work. Once configured, you will see a Gitea option when

Weblate currently supports Git (with extended support for GitHub pull requests, GitLab merge requests, Gitea pull requests, Gerrit and Subversion) and Mercurial as version control back-ends. Accessing repositories GITLAB_USERNAME, GITLAB_TOKEN, GITLAB_CREDENTIALS Gitea pull requests New in version 4.12. This just adds a thin layer atop Git using the Gitea API [https://docs.gitea.io/en- us/api-usage/] to allow pushing translation repository, while Gitea pull requests creates pull requests. You need to configure API credentials (GITEA_CREDENTIALS) in the Weblate settings to make this work. Once configured, you will see a Gitea option when

Weblate currently supports Git (with extended support for GitHub pull requests, GitLab merge requests, Gitea pull requests, Gerrit and Subversion) and Mercurial as version control back-ends. 1.11.1 Accessing GITLAB_USERNAME, GITLAB_TOKEN, GITLAB_CREDENTIALS 1.11.5 Gitea pull requests New in version 4.12. This just adds a thin layer atop Git using the Gitea API to allow pushing translation changes as pull requests repository, while Gitea pull requests creates pull requests. You need to configure API credentials (GITEA_CREDENTIALS) in the Weblate settings to make this work. Once configured, you will see a Gitea option when