-
-
Notifications
You must be signed in to change notification settings - Fork 5.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Read & write deploy keys #671
Labels
type/feature
Completely new functionality. Can only be merged if feature freeze is not active.
Milestone
Comments
Currently you can do that with separate accounts, but I would also integrate write access for deploy keys optionally |
We do have access tokens already right? shouldn't that be enough? or do they need more "control"? |
Access tokens are bound to a user, so this grants too much access. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
type/feature
Completely new functionality. Can only be merged if feature freeze is not active.
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).The text was updated successfully, but these errors were encountered: