From bf50870c11f99a28ce7920efde15e0e2c9034b0e Mon Sep 17 00:00:00 2001 From: Km Date: Sat, 3 Feb 2024 21:34:59 +0100 Subject: [PATCH 1/3] Explained where create template For some user (as me), documentation lack of precision about where to store issue/pr template. I propose an enhancement about this point. With bold exergue and precision about server itself. --- docs/content/usage/issue-pull-request-templates.en-us.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/content/usage/issue-pull-request-templates.en-us.md b/docs/content/usage/issue-pull-request-templates.en-us.md index 34475e3465888..0895d12868acc 100644 --- a/docs/content/usage/issue-pull-request-templates.en-us.md +++ b/docs/content/usage/issue-pull-request-templates.en-us.md @@ -19,9 +19,10 @@ menu: Some projects have a standard list of questions that users need to answer when creating an issue or pull request. Gitea supports adding templates to the -main branch of the repository so that they can autopopulate the form when users are +**main branch of the repository** so that they can autopopulate the form when users are creating issues and pull requests. This will cut down on the initial back and forth of getting some clarifying details. +Is actually not possible to provide generic issue/pull-request templates fort all instance. Additionally, the New Issue page URL can be suffixed with `?title=Issue+Title&body=Issue+Text` and the form will be populated with those strings. Those strings will be used instead of the template if there is one. From 371c109b33b394e872a25bd8b5b292eefae4008f Mon Sep 17 00:00:00 2001 From: 6543 <6543@obermui.de> Date: Mon, 19 Feb 2024 10:51:33 +0100 Subject: [PATCH 2/3] Update docs/content/usage/issue-pull-request-templates.en-us.md Co-authored-by: Lunny Xiao --- docs/content/usage/issue-pull-request-templates.en-us.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/usage/issue-pull-request-templates.en-us.md b/docs/content/usage/issue-pull-request-templates.en-us.md index 0895d12868acc..1ccecff84cda6 100644 --- a/docs/content/usage/issue-pull-request-templates.en-us.md +++ b/docs/content/usage/issue-pull-request-templates.en-us.md @@ -22,7 +22,7 @@ when creating an issue or pull request. Gitea supports adding templates to the **main branch of the repository** so that they can autopopulate the form when users are creating issues and pull requests. This will cut down on the initial back and forth of getting some clarifying details. -Is actually not possible to provide generic issue/pull-request templates fort all instance. +Is actually not possible to provide generic issue/pull-request templates for all instance. Additionally, the New Issue page URL can be suffixed with `?title=Issue+Title&body=Issue+Text` and the form will be populated with those strings. Those strings will be used instead of the template if there is one. From c35c84cac5badfe4787aadda01c0979fda1eea42 Mon Sep 17 00:00:00 2001 From: Km Date: Mon, 19 Feb 2024 15:44:09 +0100 Subject: [PATCH 3/3] Prefere default wording Default branch is better to use --- docs/content/usage/issue-pull-request-templates.en-us.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/usage/issue-pull-request-templates.en-us.md b/docs/content/usage/issue-pull-request-templates.en-us.md index 1ccecff84cda6..7da72fd5ddbaf 100644 --- a/docs/content/usage/issue-pull-request-templates.en-us.md +++ b/docs/content/usage/issue-pull-request-templates.en-us.md @@ -19,7 +19,7 @@ menu: Some projects have a standard list of questions that users need to answer when creating an issue or pull request. Gitea supports adding templates to the -**main branch of the repository** so that they can autopopulate the form when users are +**default branch of the repository** so that they can autopopulate the form when users are creating issues and pull requests. This will cut down on the initial back and forth of getting some clarifying details. Is actually not possible to provide generic issue/pull-request templates for all instance.