From 47ef41da3b3c55d2781d3eef5097c1a5cea30057 Mon Sep 17 00:00:00 2001 From: silverwind Date: Mon, 23 Mar 2026 19:12:49 +0000 Subject: [PATCH] Add `DEFAULT_DELETE_BRANCH_AFTER_MERGE` to config cheat sheet (#367) Add documentation for the new `[repository.pull-request]` `DEFAULT_DELETE_BRANCH_AFTER_MERGE` config option added in https://github.com/go-gitea/gitea/pull/36917. *This comment was written by Claude.* Reviewed-on: https://gitea.com/gitea/docs/pulls/367 Reviewed-by: TheFox0x7 <95654+thefox0x7@noreply.gitea.com> Co-authored-by: silverwind Co-committed-by: silverwind --- docs/administration/config-cheat-sheet.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/administration/config-cheat-sheet.md b/docs/administration/config-cheat-sheet.md index 23db55dd..dbfbd0f2 100644 --- a/docs/administration/config-cheat-sheet.md +++ b/docs/administration/config-cheat-sheet.md @@ -169,6 +169,7 @@ In addition, there is _`StaticRootPath`_ which can be set as a built-in at build - `ADD_CO_COMMITTER_TRAILERS`: **true**: Add co-authored-by and co-committed-by trailers to merge commit messages if committer does not match author. - `TEST_CONFLICTING_PATCHES_WITH_GIT_APPLY`: **false**: PR patches are tested using a three-way merge method to discover if there are conflicts. If this setting is set to **true**, conflicting patches will be retested using `git apply` - This was the previous behaviour in 1.18 (and earlier) but is somewhat inefficient. Please report if you find that this setting is required. - `RETARGET_CHILDREN_ON_MERGE`: **true**: Retarget child pull requests to the parent pull request branch target on merge of parent pull request. It only works on merged PRs where the head and base branch target the same repo. +- `DEFAULT_DELETE_BRANCH_AFTER_MERGE`: **false**: Set the default value for "Delete pull request branch after merge by default" for new repositories. ### Repository - Issue (`repository.issue`)