Read & write deploy keys #234

New Issue

GiteaMirror · 2025-11-02T03:14:54-06:00

GiteaMirror commented

2025-11-02 03:14:54 -06:00

Originally created by @GeoffreyFrogeye on GitHub (Jan 14, 2017).

Being able to give write access to some deploy keys would be very useful for repositories where git is used as an archiving and propagation tool rather than a code versioning system. Such repositories include those used by tools like pass, etckeeper, and some dotfiles manager, where commits and push can be done semi-automatically and you don't want that tool to have a write access to all your repositories.

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/40957289-read-write-deploy-keys?utm_campaign=plugin&utm_content=tracker%2F47456670&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F47456670&utm_medium=issues&utm_source=github).

Originally created by @GeoffreyFrogeye on GitHub (Jan 14, 2017). Being able to give write access to some deploy keys would be very useful for repositories where git is used as an archiving and propagation tool rather than a code versioning system. Such repositories include those used by tools like [pass](https://www.passwordstore.org/), [etckeeper](http://etckeeper.branchable.com/), and some dotfiles manager, where commits and push can be done semi-automatically and you don't want that tool to have a write access to all your repositories. <bountysource-plugin> --- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/40957289-read-write-deploy-keys?utm_campaign=plugin&utm_content=tracker%2F47456670&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F47456670&utm_medium=issues&utm_source=github). </bountysource-plugin>

GiteaMirror added the type/feature label 2025-11-02 03:14:54 -06:00

GiteaMirror closed this issue

2025-11-02 03:14:54 -06:00

GiteaMirror commented

2025-11-02 03:14:55 -06:00

@tboerger commented on GitHub (Jan 14, 2017):

Currently you can do that with separate accounts, but I would also integrate write access for deploy keys optionally

@tboerger commented on GitHub (Jan 14, 2017): Currently you can do that with separate accounts, but I would also integrate write access for deploy keys optionally

GiteaMirror commented

2025-11-02 03:14:55 -06:00

@bkcsoft commented on GitHub (Jan 14, 2017):

We do have access tokens already right? shouldn't that be enough? or do they need more "control"?

@bkcsoft commented on GitHub (Jan 14, 2017): We do have access tokens already right? shouldn't that be enough? or do they need more "control"?

GiteaMirror commented

2025-11-02 03:14:55 -06:00

@tboerger commented on GitHub (Jan 16, 2017):

Access tokens are bound to a user, so this grants too much access.

@tboerger commented on GitHub (Jan 16, 2017): Access tokens are bound to a user, so this grants too much access.

GiteaMirror referenced this issue

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