github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-09 12:46:42 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

[PR #3694] [MERGED] Change title to existing locale entry for protected branch settings #17047

New Issue
Closed
opened 2025-11-02 12:25:03 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-02 12:25:03 -06:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/go-gitea/gitea/pull/3694
Author: @Chri-s
Created: 3/19/2018
Status: ✅ Merged
Merged: 3/21/2018
Merged by: @lafriks

Base: master ← Head: protected-branch-title-fix

📝 Commits (5)

  • 91098c4 Change title to existing locale entry
  • 2f56be0 Merge branch 'master' into protected-branch-title-fix
  • 6fbb039 Merge branch 'master' into protected-branch-title-fix
  • f596ed8 Merge branch 'master' into protected-branch-title-fix
  • 51c88d4 Merge branch 'master' into protected-branch-title-fix

📊 Changes

1 file changed (+1 additions, -1 deletions)

View changed files

📝 routers/repo/setting_protected_branch.go (+1 -1)

📄 Description

The title of the settings page for a protected branch references an invalid entry in the locale. Because of this, the title of the settings page looks like this: settings.protected_branches - master - Gitea: Git with a cup of tea

The correct entry is repo.settings.protected_branch instead of repo.settings.protected_branches. With this change, the title looks like this: Branch Protection - master - Gitea: Git with a cup of tea

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/go-gitea/gitea/pull/3694 **Author:** [@Chri-s](https://github.com/Chri-s) **Created:** 3/19/2018 **Status:** ✅ Merged **Merged:** 3/21/2018 **Merged by:** [@lafriks](https://github.com/lafriks) **Base:** `master` ← **Head:** `protected-branch-title-fix` --- ### 📝 Commits (5) - [`91098c4`](https://github.com/go-gitea/gitea/commit/91098c44aed1f8d0d460d6e7d7a6449d5ac0a84d) Change title to existing locale entry - [`2f56be0`](https://github.com/go-gitea/gitea/commit/2f56be0bb3dbb74f260cac8ab09979804d56dbf5) Merge branch 'master' into protected-branch-title-fix - [`6fbb039`](https://github.com/go-gitea/gitea/commit/6fbb039f310d05836f0e12404d82bf8306fdaf9e) Merge branch 'master' into protected-branch-title-fix - [`f596ed8`](https://github.com/go-gitea/gitea/commit/f596ed80ccf4175b4a3873d6bc48a23b42dcdf7b) Merge branch 'master' into protected-branch-title-fix - [`51c88d4`](https://github.com/go-gitea/gitea/commit/51c88d44410a97c659a482da899d84972f9db7bc) Merge branch 'master' into protected-branch-title-fix ### 📊 Changes **1 file changed** (+1 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `routers/repo/setting_protected_branch.go` (+1 -1) </details> ### 📄 Description The title of the settings page for a protected branch references an invalid entry in the locale. Because of this, the title of the settings page looks like this: `settings.protected_branches - master - Gitea: Git with a cup of tea` The correct entry is `repo.settings.protected_branch` instead of `repo.settings.protected_branches`. With this change, the title looks like this: `Branch Protection - master - Gitea: Git with a cup of tea` --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2025-11-02 12:25:03 -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 pull-request
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#17047
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?