github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-05-25 20:10:47 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Issue and PR templates #1518

New Issue
Closed
opened 2025-11-02 04:03:41 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2025-11-02 04:03:41 -06:00
Owner
Copy Link

Originally created by @lapin-b on GitHub (Feb 11, 2018).

  • Gitea version (or commit ref): 1.4.0+rc1
  • Git version: 2.16.1
  • Operating system: Linux (Arch Linux)
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:
    Not relevant

Description

I have absolutely no idea how I can word this, but I'll do my best.

In a nutshell, if the template file exists in the repository (let's say .gitea/ISSUE_TEMPLATE.md), then Gitea can fetch the contents of the file and populate the textarea on the new issue template. Otherwise leave the textarea empty.

For example, GitHub implements this feature.

PS: my wording can be terrible; English isn't my native language

Originally created by @lapin-b on GitHub (Feb 11, 2018). <!-- 1. Please speak English, this is the language all of us can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/NsatcWJ) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report. --> - Gitea version (or commit ref): 1.4.0+rc1 - Git version: 2.16.1 - Operating system: Linux (Arch Linux) - Database (use `[x]`): - [ ] PostgreSQL - [x] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x] Not relevant - Log gist: *Not relevant* ## Description I have absolutely no idea how I can word this, but I'll do my best. In a nutshell, if the template file exists in the repository (let's say `.gitea/ISSUE_TEMPLATE.md`), then Gitea can fetch the contents of the file and populate the textarea on the new issue template. Otherwise leave the textarea empty. For example, GitHub implements this feature. *PS: my wording can be terrible; English isn't my native language*
GiteaMirror added the type/docs label 2025-11-02 04:03:41 -06:00
GiteaMirror commented 2025-11-02 04:03:42 -06:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Feb 13, 2018):

This actually already exists:

Possible names for issues:

"ISSUE_TEMPLATE.md",
"issue_template.md",
".gitea/ISSUE_TEMPLATE.md",
".gitea/issue_template.md",
".github/ISSUE_TEMPLATE.md",
".github/issue_template.md",

And for PRs:

"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",

We should add this somewhere to the docs.

@kolaente commented on GitHub (Feb 13, 2018): This actually already exists: Possible names for issues: ``` "ISSUE_TEMPLATE.md", "issue_template.md", ".gitea/ISSUE_TEMPLATE.md", ".gitea/issue_template.md", ".github/ISSUE_TEMPLATE.md", ".github/issue_template.md", ``` And for PRs: ``` "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", ``` We should add this somewhere to the docs.
GiteaMirror commented 2025-11-02 04:03:42 -06:00
Author
Owner
Copy Link

@techknowlogick commented on GitHub (May 10, 2018):

@kolaente I added a PR to add this information to the docs, please see: #3942

@techknowlogick commented on GitHub (May 10, 2018): @kolaente I added a PR to add this information to the docs, please see: #3942
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label type/docs
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#1518
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?