I'd like to be able to limit access so that a release manager could submit tags, but can't submit code changes. (Because our release manager also is a developer.) At some level I realize that this could be done with human process enforcement, but I'm wondering if the tool can provide an extra level of caution.
In fact, what I'd really like to do is be able to create a deployment key that allows pulling, *and tagging*, but nothing else. Is it possible?
Alternatively, a way to push a tag from the UI would be great.
Thanks.
Please open a feature request at https://bitbucket.org/site/master/issues/new for consideration. I think the idea of allowing tagging through the UI or API would probably be more likely than partial write permissions to a repo.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.