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: README.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,15 +35,15 @@ OnCheckForUpdates←{
35
35
0⊣#.APLTreeUtils2.GoToWebPage data.zipball_url
36
36
}
37
37
```
38
-
Note that there is also a CheckForUpdate method that takes a repository name and a version number (typically the currently installed/used version). It returns an empty vector if no better version is available, or the better version number.
38
+
Note that there is also a `CheckForUpdate` method that takes a repository name and a version number (typically the currently installed/used version). It returns an empty vector if no better version is available, or the better version number.
39
39
40
40
## Authentication and authorisation
41
41
42
-
At present, authentication and authorization are not necessary since all methods are read-only.
42
+
At present, authentication and authorization are not required since all methods are read-only.
43
43
44
-
However, two potential scenarios may require attention to authentication and authorization:
44
+
However, two potential scenarios may require authentication and authorization anyway:
45
45
46
-
*Addition of methods in future versions that require write access (e.g.,`CreateIssue`and similar operations)
46
+
*In the future methods might be added that require write access like`CreateIssue`etc.
47
47
* Severe limitations on the number of requests per hour without authentication/authorization
48
48
49
49
To address these scenarios, you must create a personal access token on the GitHub website and assign it to the instance property "personal_access_token".
0 commit comments