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

Support GitHub .config.yml functionality #7229

New Issue
Open
opened 2025-11-02 07:20:16 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-02 07:20:16 -06:00
Owner
Copy Link

Originally created by @Reinitialized on GitHub (Apr 21, 2021).

As a user of Gitea, I've noticed a lack of support for:

  • disabling creating a blank issue when templates are available
  • adding redirects to urls for certain actions

Example of how I would like my "New Issues" page to look like:
image

Example of how this was configured:
https://github.com/pi-hole/.github/blob/master/.github/ISSUE_TEMPLATE/config.yml

Additionally, it would be nice to be able to create a repo containing all of this data within an organization, and have it apply to every repo by default. Example being https://github.com/pi-hole/.github

Originally created by @Reinitialized on GitHub (Apr 21, 2021). As a user of Gitea, I've noticed a lack of support for: - disabling creating a blank issue when templates are available - adding redirects to urls for certain actions Example of how I would like my "New Issues" page to look like: ![image](https://user-images.githubusercontent.com/20674500/115622661-c4405080-a2bd-11eb-971e-b5eba5cedb06.png) Example of how this was configured: https://github.com/pi-hole/.github/blob/master/.github/ISSUE_TEMPLATE/config.yml Additionally, it would be nice to be able to create a repo containing all of this data within an organization, and have it apply to every repo by default. Example being https://github.com/pi-hole/.github
GiteaMirror added the type/featuretype/proposal labels 2025-11-02 07:20:16 -06:00
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/feature type/proposal
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#7229
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?