Project wide API Key / Token, not just User specific
We’d like to integrate the MR process with our deploy and notification processes, and making requests to the API to get MR info is the best way to do this for us. Unfortunately, it looks like I have to pass a user’s private token (or an OAUTH token) per the docs: http://doc.gitlab.com/ee/api/README.html
We’d like to be able to use a token in our config, without having to use a specific user account.
Possible Solution: Allow the creation of an API key / token that has access to a specific project, without being tied to a particular user.
Possible Addition: 1 or more API keys with various permissions, to control access certain applications have to the Project. (some with Read only, some with write/Comment access etc.)