You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
gitea/docs/content/doc/advanced
zeripath 198342efe4
Add setting to disable the git apply step in test patch (#22130) (#22170)
Backport #22130

For a long time Gitea has tested PR patches using a git apply --check
method, and in fact prior to the introduction of a read-tree assisted
three-way merge in #18004, this was the only way of checking patches.

Since #18004, the git apply --check method has been a fallback method,
only used when the read-tree three-way merge method has detected a
conflict. The read-tree assisted three-way merge method is much faster
and less resource intensive method of detecting conflicts. #18004 kept
the git apply method around because it was thought possible that this
fallback might be able to rectify conflicts that the read-tree three-way
merge detected. I am not certain if this could ever be the case.

Given the uncertainty here and the now relative stability of the
read-tree method - this PR makes using this fallback optional but
enables it by default. A `log.Critical` has been added which will alert
if the `git apply --check` method was successful at checking a PR that
`read-tree` failed on.

The hope is that none of these log.Critical messages will be found and
there will be no significant difference in conflict detection. Thus we
will be able to remove the git apply fallback in future, and/or improve
the read-tree three-way merge method to catch any conflicts that git
apply method might have been able to fix.

An additional benefit for anyone who disables the check method is that
patch checking should be significantly less resource intensive and much
quicker.

(See
https://github.com/go-gitea/gitea/issues/22083\#issuecomment-1347961737)

Ref #22083

Signed-off-by: Andrew Thornton <art27@cantab.net>

<!--

Please check the following:

1. Make sure you are targeting the `main` branch, pull requests on
release branches are only allowed for bug fixes.
2. Read contributing guidelines:
https://github.com/go-gitea/gitea/blob/main/CONTRIBUTING.md
3. Describe what your pull request does and which issue you're targeting
(if any)

-->

Signed-off-by: Andrew Thornton <art27@cantab.net>
Co-authored-by: KN4CK3R <admin@oldschoolhack.me>
2 years ago
..
adding-legal-pages.en-us.md Fix various typos of software names (#18083) 3 years ago
clone-filter.en-us.md Add markdownlint (#20512) 3 years ago
cmd-embedded.en-us.md Fix various typos of software names (#18083) 3 years ago
config-cheat-sheet.en-us.md Add setting to disable the git apply step in test patch (#22130) (#22170) 2 years ago
config-cheat-sheet.zh-cn.md Clarify that `ENABLE_SWAGGER` only influences the API docs, not the routes (#21215) 2 years ago
customizing-gitea.en-us.md Fix PlantUML example in document (#21142) 2 years ago
customizing-gitea.zh-cn.md Update documentation to reflect #15219 (#16442) 4 years ago
environment-variables.en-us.md Update docs and comments to remove macaron (#14491) 4 years ago
environment-variables.zh-cn.md Add markdownlint (#20512) 3 years ago
external-renderers.en-us.md Add KaTeX rendering to Markdown. (#20571) 2 years ago
hacking-on-gitea.zh-cn.md ZH-CN translation of Advanced part (#5090) 6 years ago
logging-documentation.en-us.md Upgrade the document about how to collect logs for systemd and docker (#21101) 3 years ago
mail-templates-us.md Add markdownlint (#20512) 3 years ago
make.fr-fr.md docs: fix various typos and translate to french (#16477) 4 years ago
make.zh-cn.md Reformat docs (#13897) 4 years ago
protected-tags.en-us.md Add markdownlint (#20512) 3 years ago
repo-indexer.en-us.md Reformat docs (#13897) 4 years ago
repo-mirror.en-us.md Add markdownlint (#20512) 3 years ago
search-engines-indexation.en-us.md Add markdownlint (#20512) 3 years ago
signing.en-us.md Add hint to GNUPGHOME environment variable (#20134) 3 years ago
third-party-tools.zh-cn.md Add markdownlint (#20512) 3 years ago