forked from gitea/gitea
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. I've found some user with same interrogation as : https://forum.gitea.com/t/issue-template-directory/3328 --------- Co-authored-by: Km <cam.lafit@azerttyu.net> Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
This commit is contained in:
parent
ade1110e8b
commit
3f73eabb66
|
@ -19,9 +19,10 @@ menu:
|
||||||
|
|
||||||
Some projects have a standard list of questions that users need to answer
|
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
|
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
|
creating issues and pull requests. This will cut down on the initial back and forth
|
||||||
of getting some clarifying details.
|
of getting some clarifying details.
|
||||||
|
It is currently not possible to provide generic issue/pull-request templates globally.
|
||||||
|
|
||||||
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.
|
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.
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue