Skip to content

Commit 79ee621

Browse files
Added missing options to the page
1 parent ffd6b88 commit 79ee621

File tree

1 file changed

+22
-0
lines changed

1 file changed

+22
-0
lines changed

user/web-ui.md

Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -21,6 +21,28 @@ If *OFF*, builds won't run on pushed commits on branches.
2121

2222
If *ON*, builds will be run on new [pull requests](/user/pull-requests/).
2323

24+
## User Management
25+
26+
Simple 'trigger build' control. Allow or prevent users with appropriate access to the repository to trigger a build for the repository. By default, all synchronized users with access to the repository are allowed to trigger a build.
27+
28+
## Share encrypted variables with forks
29+
30+
In the case of a fork-to-base pull request:
31+
32+
If this setting is ON, the encrypted environment variables will be available to the forked repository, which means that builds in the forked repository will have access to the encrypted environment variables from the base repository. This may be a less secure approach yet allows for a collaboration using forks and Pull Requests (PRs).
33+
If this setting is OFF and the build relies on any encrypted environment variable, the PR from fork to base repository will fail. This secures your base repository encrypted environmental variables by putting a constraint on accessing them from forks.
34+
35+
Read more: [Pull Requests and security restrictions](/user/pull-requests#pull-requests-and-security-restrictions)
36+
37+
## Share SSH Keys with forks
38+
39+
In the case of a fork-to-base pull request:
40+
41+
if this setting is ON, the custom SSH keys from the base repository will be available to the forked repository, which means that the build in the forked repository will be able to use the custom SSH keys from the base repository. Consider setting to ON if your collaboration model requires working with Pull Requests (PRs) from forked repositories or there are dependencies defined, which rely on SSH key from base repository.
42+
If this setting is OFF and the build is relying on custom SSH keys i.e. for fetching some additional dependencies, it will fail with a no access error.
43+
44+
Read more: [Pull Requests and security restrictions](/user/pull-requests#pull-requests-and-security-restrictions)
45+
2446
## Auto cancel branch builds
2547

2648
{{ site.data.snippets.auto_cancellation }}

0 commit comments

Comments
 (0)