NYANDEV/forgejo
NYANDEV/forgejo
4
0
Fork 1
mirror of https://codeberg.org/forgejo/forgejo.git synced 2024-12-26 20:27:03 +01:00
Code Issues 2 Projects 1 Releases Packages Wiki Activity
forgejo/docs/content/doc/usage/issue-pull-request-templates.en-us.md
kekero 3568d426fe New Issue ?body= query (#5851) 
* New Issue ?body= query

* Override issue template with body query

* Add documentation for issue body query
2019-01-28 10:23:59 -05:00

1.3 KiB
Raw Blame History

date title slug weight toc draft menu
2018-05-10T16:00:00+02:00 Usage: Issue and Pull Request templates issue-pull-request-templates 15 true false
sidebar
parent name weight identifier
usage Issue and Pull Request templates 15 issue-pull-request-templates

Issue and Pull Request Templates

For some projects there are a standard list of questions that users need to be asked for creating an issue, or adding a 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.

Possible file names for issue templates:

  • ISSUE_TEMPLATE.md
  • issue_template.md
  • .gitea/ISSUE_TEMPLATE.md
  • .gitea/issue_template.md
  • .github/ISSUE_TEMPLATE.md
  • .github/issue_template.md

Possible file names for PR templates:

  • PULL_REQUEST_TEMPLATE.md
  • pull_request_template.md
  • .gitea/PULL_REQUEST_TEMPLATE.md
  • .gitea/pull_request_template.md
  • .github/PULL_REQUEST_TEMPLATE.md
  • .github/pull_request_template.md

Additionally, the New Issue page URL can be suffixed with ?body=Issue+Text and the form will be populated with that string. This string will be used instead of the template if there is one.