Any plan to use GitLab's "Project access tokens" feature for integration with Bot accounts?

GitLab recently released "Project access tokens" as a feature in their 13. release (and enabled them by default in 13.3) for self-hosted instances. Though they plan on releasing it for Gitlab.com instances the 13.4 release (as per this comment on their issue page: https://gitlab.com/gitlab-org/gitlab/-/issues/6883#note_395769725).

Here's the wiki page for the feature: https://docs.gitlab.com/ee/user/project/settings/project_access_tokens.html 

As it stands, using the GitLab integration requires creating a new account, which means paying for a new user. The new feature still requires us to pay for these service account bots, but this is an issue they are planning on fixing as per this issue (which is also mentioned in the feature page linked above): https://gitlab.com/gitlab-org/gitlab/-/issues/223695

Are there any plans on changing the current integration implementation over to these project access tokens so that we won't need to pay for an extra seat to use the ClubHouse integration (once GitLab fixes the aforementioned issue, of course)?

Didn't find what you were looking for?

New post
Would you like to add your +1 to this post?
1 out of 1 found this helpful

Comments

0 comments

Please sign in to leave a comment.