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
Copy file name to clipboardExpand all lines: user/assembla-oauth-scopes.md
+4-2Lines changed: 4 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ some of your data on Assembla. Read the
10
10
[Scopes for the Assembla REST API](https://api-docs.assembla.cc/)
11
11
for general information about this, or pick an explanation of what data we need and why we need it.
12
12
13
-
## Travis CI for OpenSource and Private Projects
13
+
## Travis CI for Open-Source and Private Projects
14
14
15
15
On <https://travis-ci.com>, via our Assembla integration, we ask for the following permissions:
16
16
@@ -24,6 +24,8 @@ We use scoped OAuth tokens to integrate with Assembla.
24
24
25
25
## Used Scopes
26
26
27
+
The following sections show the different scopes used.
28
+
27
29
### repository
28
30
It gives the app read access to all the repositories the authorizing user has access to.
29
31
> This scope does not give access to a repository's pull requests.
@@ -32,7 +34,7 @@ It gives the app read access to all the repositories the authorizing user has ac
32
34
It gives the app admin access to all the repositories the authorizing user has access to. This permission is needed to add the access key. Travis CI uses the key to read the travis.yml file content.
33
35
34
36
35
-
### pullrequest
37
+
### pull-request
36
38
It gives the app read access to pull requests and collaborate on them. This scope implies a repository giving read access to the pull request's destination repository.
When you sign in to Travis CI for the first time, we ask for permissions to access
8
+
When you sign in to Travis CI for the first time, we ask for permission to access
9
9
some of your data on Bitbucket. Read the
10
10
[Scopes for the Bitbucket Cloud REST API](https://developer.atlassian.com/cloud/bitbucket/bitbucket-cloud-rest-api-scopes/)
11
11
for general information about this, or pick an explanation of what data we need and why we need it.
12
12
13
-
## Travis CI for OpenSource and Private Projects
13
+
## Travis CI for Open-Source and Private Projects
14
14
15
15
On <https://travis-ci.com>, via our Bitbucket integration, we ask for the following permissions:
16
16
@@ -24,15 +24,17 @@ We use scoped OAuth tokens to integrate with Bitbucket.
24
24
25
25
## Used Scopes
26
26
27
+
The following sections explain the different scopes used.
28
+
27
29
### repository
28
-
Gives the app read access to all the repositories the authorizing user has access to.
30
+
It gives the app read access to all the repositories the authorizing user has access to.
29
31
> This scope does not give access to a repository's pull requests.
30
32
31
33
### repository:admin
32
34
Gives the app admin access to all the repositories the authorizing user has access to. This permission is needed to add the access key. Travis CI uses the key to read the travis.yml file content.
33
35
34
36
35
-
### pullrequest
37
+
### pull-request
36
38
Gives the app read access to pull requests and collaborate on them. This scope implies repository, giving read access to the pull request's destination repository.
37
39
38
40
### email
@@ -45,9 +47,9 @@ Ability to see all the user's account information. Note that this does not inclu
45
47
The ability to find out what teams the current user is part of. This is covered by the teams endpoint.
46
48
47
49
### webhook
48
-
Gives access to webhooks. This scope is required for any webhookrelated operation.
50
+
Gives access to webhooks. This scope is required for any webhook-related operation.
49
51
50
-
This scope gives read access to existing webhook subscriptions on all resources you can access, without needing further scopes.
52
+
This scope gives read access to existing webhook subscriptions to all resources you can access, without needing further scopes.
51
53
This means that a client can list all existing webhook subscriptions on repository foo/bar (assuming the principal user has access
52
54
to this repo). The additional repository scope is not required for this.
0 commit comments