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

no documentation on how to configure deploy keys #10734

New Issue
Closed
opened 2025-11-02 09:16:57 -06:00 by GiteaMirror · 5 comments
GiteaMirror commented 2025-11-02 09:16:57 -06:00
Owner
Copy Link

Originally created by @GDMTT on GitHub (Apr 27, 2023).

Description

Hi,

I can't find anything in the Gitea documentation on how to configure Deploy keys. I'm specifically looking for windows related instrucitons.

Thank you.

Gitea Version

1.18.5

Can you reproduce the bug on the Gitea demo site?

Yes

Log Gist

No response

Screenshots

No response

Git Version

2.39.1.windows.1

Operating System

Windows Client

How are you running Gitea?

K3s install using this guide: https://github.com/kurokobo/awx-on-k3s/tree/main/git

Database

None

Originally created by @GDMTT on GitHub (Apr 27, 2023). ### Description Hi, I can't find anything in the Gitea documentation on how to configure Deploy keys. I'm specifically looking for windows related instrucitons. Thank you. ### Gitea Version 1.18.5 ### Can you reproduce the bug on the Gitea demo site? Yes ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version 2.39.1.windows.1 ### Operating System Windows Client ### How are you running Gitea? K3s install using this guide: https://github.com/kurokobo/awx-on-k3s/tree/main/git ### Database None
GiteaMirror added the issue/needs-feedback label 2025-11-02 09:16:57 -06:00
GiteaMirror commented 2025-11-02 09:16:58 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Apr 27, 2023):

The UI could be slightly different, but it's indeed on the setting page.

image

@wxiaoguang commented on GitHub (Apr 27, 2023): The UI could be slightly different, but it's indeed on the setting page. ![image](https://user-images.githubusercontent.com/2114189/234771540-9656fb9b-ad37-48e8-b141-f9156ece5bab.png)
GiteaMirror commented 2025-11-02 09:16:58 -06:00
Author
Owner
Copy Link

@dpedu commented on GitHub (Jun 9, 2023):

Issues aren't documentation, this should stay open.

@dpedu commented on GitHub (Jun 9, 2023): Issues aren't documentation, this should stay open.
GiteaMirror commented 2025-11-02 09:16:59 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Jun 10, 2023):

@dpedu could you help to propose a PR for updating the document?

@wxiaoguang commented on GitHub (Jun 10, 2023): @dpedu could you help to propose a PR for updating the document?
GiteaMirror commented 2025-11-02 09:16:59 -06:00
Author
Owner
Copy Link

@dpedu commented on GitHub (Jun 21, 2023):

@wxiaoguang I cannot as I am unfamiliar with the feature in question, because it is undocumented and I am unfamiliar with gitea's internals.

@dpedu commented on GitHub (Jun 21, 2023): @wxiaoguang I cannot as I am unfamiliar with the feature in question, because it is undocumented and I am unfamiliar with gitea's internals.
GiteaMirror commented 2025-11-02 09:16:59 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Jun 22, 2023):

From my side, I don't see anything unclear for it. This feature just exists, and it is in the top-level menu on the setting page. Just like "Branches", "Tags", there is no document either, there is no document for "change avatar" or "change email" either.

I agree that document could be written for everything, but I also agree if a feature is clear, then it can be used by intuition without document.

If you think "deploy key" needs a document, please help to elaborate about how to write a better document for it, since the project is open source and crowd-contributed, I will be happy to review.

@wxiaoguang commented on GitHub (Jun 22, 2023): From my side, I don't see anything unclear for it. This feature just exists, and it is in the top-level menu on the setting page. Just like "Branches", "Tags", there is no document either, there is no document for "change avatar" or "change email" either. I agree that document could be written for everything, but I also agree if a feature is clear, then it can be used by intuition without document. If you think "deploy key" needs a document, please help to elaborate about how to write a better document for it, since the project is open source and crowd-contributed, I will be happy to review.
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 issue/needs-feedback
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#10734
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?