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

Option To Sign Web Interface Commits By Full Name Or Username #9255

New Issue
Open
opened 2025-11-02 08:33:21 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-02 08:33:21 -06:00
Owner
Copy Link

Originally created by @Deadmano on GitHub (Jul 22, 2022).

Feature Description

Currently if you set a full name, despite setting DEFAULT_SHOW_FULL_NAME to false it will still commit messages on the web interface with the author set to your full name. Emptying the full name field sets the author name to your username.

Am I missing the point of the profile and having a full name present to identify when using an alias/username? Because as it stands, if you want commit messages from any CRUD operation via the web interface to be authored under your username you cannot have a full name set. This in turn causes a mismatch in git history where you may have a local username set which differs if performing web operations as a result of the full name taking priority.

Screenshots

No response

Originally created by @Deadmano on GitHub (Jul 22, 2022). ### Feature Description Currently if you set a full name, despite setting `DEFAULT_SHOW_FULL_NAME` to `false` it will still commit messages on the web interface with the author set to your full name. Emptying the full name field sets the author name to your username. Am I missing the point of the profile and having a full name present to identify when using an alias/username? Because as it stands, if you want commit messages from any CRUD operation via the web interface to be authored under your username you cannot have a full name set. This in turn causes a mismatch in `git history` where you may have a local username set which differs if performing web operations as a result of the full name taking priority. ### Screenshots _No response_
GiteaMirror added the type/proposaltype/feature labels 2025-11-02 08:33:21 -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#9255
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?