feature request: add organisation wide deploy key #5003

New Issue

GiteaMirror · 2025-11-02T06:10:41-06:00

GiteaMirror commented

2025-11-02 06:10:41 -06:00

Originally created by @jclain on GitHub (Mar 5, 2020).

Gitea version (or commit ref): 1.10.3
Git version: not relevant
Operating system: Linux
Database (use [x]):
- PostgreSQL
- MySQL
- MSSQL
- SQLite
Can you reproduce the bug at https://try.gitea.io:
- Yes (provide example URL)
- No
- Not relevant
Log gist:

Description

there already is org-wide webhook. have you considered adding org-wide deploy key?
I'd like to be able to automatically build / deploy all repositories in an organisation, but for now I have to add the deployment ssh key to each repo individually

TIA, regards,
Jephté

Originally created by @jclain on GitHub (Mar 5, 2020). - Gitea version (or commit ref): 1.10.3 - Git version: not relevant - Operating system: Linux - Database (use `[x]`): - [ ] PostgreSQL - [x] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x] Not relevant - Log gist: ## Description there already is org-wide webhook. have you considered adding org-wide deploy key? I'd like to be able to automatically build / deploy all repositories in an organisation, but for now I have to add the deployment ssh key to each repo individually TIA, regards, Jephté

GiteaMirror added the type/proposal label 2025-11-02 06:10:41 -06:00

GiteaMirror closed this issue

2025-11-02 06:10:41 -06:00

GiteaMirror commented

2025-11-02 06:10:42 -06:00

@lafriks commented on GitHub (Mar 11, 2020):

As a workaround is to create service user to add to the organization team with needed rights

@lafriks commented on GitHub (Mar 11, 2020): As a workaround is to create service user to add to the organization team with needed rights

GiteaMirror commented

2025-11-02 06:10:42 -06:00

@jclain commented on GitHub (Mar 12, 2020):

yes... indeed... don't know why I didn't think about this :-/
also, thinking about it, it's a better solution than creating a org wide deploy key, because you can track what did which service account
well... consider my feature request closed as far as I'm concerned :-)

@jclain commented on GitHub (Mar 12, 2020): yes... indeed... don't know why I didn't think about this :-/ also, thinking about it, it's a better solution than creating a org wide deploy key, because you can track what did which service account well... consider my feature request closed as far as I'm concerned :-)

GiteaMirror referenced this issue

2025-11-02 14:14:20 -06:00

[PR #5003] [CLOSED] Clone panel overflow #17585

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#5003