You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The token needs the `PROJECT_ADMIN` and `REPOSITORY_ADMIN` permissions. It also needs access to forked repositories in pull requests, otherwise Pipelines-as-Code cannot process and access the pull request.
22
+
For detailed instructions on creating and managing access tokens, refer to the official Bitbucket Data Center documentation:
The token must have either `PROJECT_ADMIN` or `REPOSITORY_ADMIN` permissions. If Pipelines-as-Code needs to process pull requests from forked repositories, the token must also have administrative access to those forked repositories. Without this access, Pipelines-as-Code cannot retrieve the required pull request information or interact with the forked repository.
21
26
22
27
{{< callout type="info" >}}
23
28
24
-
The service account user that owns the token must be a **licensed Bitbucket
29
+
When using a personal HTTP token, the associated user must be a **licensed Bitbucket
25
30
user** (i.e., granted the `LICENSED_USER` global permission) for group-based
26
-
permission checks to work. If the service account is an unlicensed technical
31
+
permission checks to work. If the user account is an unlicensed technical
27
32
user, group membership cannot be resolved and users with group-only access
28
33
will not be able to trigger builds. As a workaround, add those users
29
34
individually to the project or repository permissions.
0 commit comments