gitea/services/packages
Rob Gonnella c9e7fde8b3
feat: adds option to force update new branch in contents routes (#35592)
Allows users to specify a "force" option in API /contents routes when
modifying files in a new branch. When "force" is true, and the branch
already exists, a force push will occur provided the branch does not
have a branch protection rule that disables force pushing.

This is useful as a way to manage a branch remotely through only the
API. For example in an automated release tool you can pull commits,
analyze, and update a release PR branch all remotely without needing to
clone or perform any local git operations.

Resolve #35538

---------

Co-authored-by: Rob Gonnella <rob.gonnella@papayapay.com>
Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
2025-10-06 21:23:14 -07:00
..
alpine Enable addtional linters (#34085) 2025-04-01 10:14:01 +00:00
arch Remove incorrect "db.DefaultContext" usages (#35366) 2025-08-28 03:52:43 +00:00
cargo feat: adds option to force update new branch in contents routes (#35592) 2025-10-06 21:23:14 -07:00
cleanup Use db.WithTx/WithTx2 instead of TxContext when possible (#35130) 2025-07-22 10:02:01 -07:00
container Remove incorrect "db.DefaultContext" usages (#35366) 2025-08-28 03:52:43 +00:00
debian Use ProtonMail/go-crypto to replace keybase/go-crypto (#33402) 2025-01-27 09:14:08 +08:00
rpm enforce explanation for necessary nolints and fix bugs (#34883) 2025-06-27 21:48:03 +08:00
auth.go Enable addtional linters (#34085) 2025-04-01 10:14:01 +00:00
package_update.go Add composor source field (#33502) 2025-02-28 16:29:21 +00:00
packages.go Use db.WithTx/WithTx2 instead of TxContext when possible (#35130) 2025-07-22 10:02:01 -07:00