Deploy keys no longer available for uninitialized repository #29060
Comments
wxiaoguang
pushed a commit
that referenced
this issue
Feb 11, 2024
Shows more settings for empty repositories (Fixes #29060)
silverwind
pushed a commit
to silverwind/gitea
that referenced
this issue
Feb 20, 2024
Shows more settings for empty repositories (Fixes go-gitea#29060)
6543
pushed a commit
to 6543-forks/gitea
that referenced
this issue
Feb 26, 2024
Shows more settings for empty repositories (Fixes go-gitea#29060) (cherry picked from commit 28db539)
|
Automatically locked because of our CONTRIBUTING guidelines |
lunny
pushed a commit
to lunny/gitea
that referenced
this issue
Apr 22, 2024
Shows more settings for empty repositories (Fixes go-gitea#29060)
lunny
added a commit
that referenced
this issue
Apr 23, 2024
Fix #30620 Manullay Backport #29130 Shows more settings for empty repositories (Fixes #29060) Co-authored-by: Tim-Nicas Oelschläger <[email protected]>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description
When creating a new repository, I need to create a deploy key for my external process to push changes. The UI for this is no longer available unless a file exists.
Screenshots
Gitea Version
1.21.5
Can you reproduce the bug on the Gitea demo site?
No
Operating System
No response
Browser Version
Safari
The text was updated successfully, but these errors were encountered: