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

Provide same PASSWORD/USERNAME keyword to all configuration option #12549

New Issue
Open
opened 2025-11-02 10:13:43 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2025-11-02 10:13:43 -06:00
Owner
Copy Link

Originally created by @camlafit on GitHub (Feb 27, 2024).

Feature Description

Hello

We have an inconsistency about password keyword, it's use PASSWORD or PASSWD without real logic

We can found some trouble about this for example at :

Could be nice to use full keyword PASSWORD in all case, and accept as workaround PASSWD during transitional version.

Thanks

Screenshots

No response

Originally created by @camlafit on GitHub (Feb 27, 2024). ### Feature Description Hello We have an inconsistency about password keyword, it's use PASSWORD or PASSWD without real logic We can found some trouble about this for example at : * https://github.com/go-gitea/gitea/issues/28335 Could be nice to use full keyword PASSWORD in all case, and accept as workaround PASSWD during transitional version. Thanks ### Screenshots _No response_
GiteaMirror added the type/proposal label 2025-11-02 10:13:43 -06:00
GiteaMirror commented 2025-11-02 10:13:44 -06:00
Author
Owner
Copy Link

@camlafit commented on GitHub (Feb 27, 2024):

To complete with have same trouble between USER and USERNAME keyword

@camlafit commented on GitHub (Feb 27, 2024): To complete with have same trouble between USER and USERNAME keyword
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/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#12549
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?