mirror of
https://github.com/bitwarden/browser
synced 2025-12-06 00:13:28 +00:00
Add comments to build workflows to indicate their intended use (#14069)
* Added comments to build workflows. * Updated comments and job names.
This commit is contained in:
8
.github/workflows/build-browser-target.yml
vendored
8
.github/workflows/build-browser-target.yml
vendored
@@ -1,3 +1,9 @@
|
||||
# This workflow is intended to be run when we need to build the client and produce artifacts that require secrets
|
||||
# when the PR source branch does not have access to secrets (e.g. a fork).
|
||||
# This workflow will run in the context of the target of the PR and have access to secrets.
|
||||
# This should only be done after reviewing the PR to ensure that no malicious code has been introduced,
|
||||
# as it could allow the code on the forked branch to have access to workflow secrets.
|
||||
|
||||
name: Build Browser on PR Target
|
||||
|
||||
on:
|
||||
@@ -25,7 +31,7 @@ jobs:
|
||||
uses: bitwarden/gh-actions/.github/workflows/check-run.yml@main
|
||||
|
||||
run-workflow:
|
||||
name: Run Build Browser on PR Target
|
||||
name: Build Browser
|
||||
needs: check-run
|
||||
if: ${{ github.event.pull_request.head.repo.full_name != github.repository }}
|
||||
uses: ./.github/workflows/build-browser.yml
|
||||
|
||||
4
.github/workflows/build-browser.yml
vendored
4
.github/workflows/build-browser.yml
vendored
@@ -1,3 +1,7 @@
|
||||
# This workflow will run in the context of the source of the PR.
|
||||
# On a PR from a fork, the workflow will not have access to secrets, and so any parts of the build that require secrets will not run.
|
||||
# If additional artifacts are needed, the failed "build-browser-target.yml" workflow held up by the check-run should be re-run.
|
||||
|
||||
name: Build Browser
|
||||
|
||||
on:
|
||||
|
||||
8
.github/workflows/build-cli-target.yml
vendored
8
.github/workflows/build-cli-target.yml
vendored
@@ -1,3 +1,9 @@
|
||||
# This workflow is intended to be run when we need to build the client and produce artifacts that require secrets
|
||||
# when the PR source branch does not have access to secrets (e.g. a fork).
|
||||
# This workflow will run in the context of the target of the PR and have access to secrets.
|
||||
# This should only be done after reviewing the PR to ensure that no malicious code has been introduced,
|
||||
# as it could allow the code on the forked branch to have access to workflow secrets.
|
||||
|
||||
name: Build CLI on PR Target
|
||||
|
||||
on:
|
||||
@@ -25,7 +31,7 @@ jobs:
|
||||
uses: bitwarden/gh-actions/.github/workflows/check-run.yml@main
|
||||
|
||||
run-workflow:
|
||||
name: Run Build CLI on PR Target
|
||||
name: Build CLI
|
||||
needs: check-run
|
||||
if: ${{ github.event.pull_request.head.repo.full_name != github.repository }}
|
||||
uses: ./.github/workflows/build-cli.yml
|
||||
|
||||
4
.github/workflows/build-cli.yml
vendored
4
.github/workflows/build-cli.yml
vendored
@@ -1,3 +1,7 @@
|
||||
# This workflow will run in the context of the source of the PR.
|
||||
# On a PR from a fork, the workflow will not have access to secrets, and so any parts of the build that require secrets will not run.
|
||||
# If additional artifacts are needed, the failed "build-cli-target.yml" workflow held up by the check-run should be re-run.
|
||||
|
||||
name: Build CLI
|
||||
|
||||
on:
|
||||
|
||||
9
.github/workflows/build-desktop-target.yml
vendored
9
.github/workflows/build-desktop-target.yml
vendored
@@ -1,3 +1,10 @@
|
||||
|
||||
# This workflow is intended to be run when we need to build the client and produce artifacts that require secrets
|
||||
# when the PR source branch does not have access to secrets (e.g. a fork).
|
||||
# This workflow will run in the context of the target of the PR and have access to secrets.
|
||||
# This should only be done after reviewing the PR to ensure that no malicious code has been introduced,
|
||||
# as it could allow the code on the forked branch to have access to workflow secrets.
|
||||
|
||||
name: Build Desktop on PR Target
|
||||
|
||||
on:
|
||||
@@ -24,7 +31,7 @@ jobs:
|
||||
uses: bitwarden/gh-actions/.github/workflows/check-run.yml@main
|
||||
|
||||
run-workflow:
|
||||
name: Run Build Desktop on PR Target
|
||||
name: Build Desktop
|
||||
needs: check-run
|
||||
if: ${{ github.event.pull_request.head.repo.full_name != github.repository }}
|
||||
uses: ./.github/workflows/build-desktop.yml
|
||||
|
||||
4
.github/workflows/build-desktop.yml
vendored
4
.github/workflows/build-desktop.yml
vendored
@@ -1,3 +1,7 @@
|
||||
# This workflow will run in the context of the source of the PR.
|
||||
# On a PR from a fork, the workflow will not have access to secrets, and so any parts of the build that require secrets will not run.
|
||||
# If additional artifacts are needed, the failed "build-desktop-target.yml" workflow held up by the check-run should be re-run.
|
||||
|
||||
name: Build Desktop
|
||||
|
||||
on:
|
||||
|
||||
8
.github/workflows/build-web-target.yml
vendored
8
.github/workflows/build-web-target.yml
vendored
@@ -1,3 +1,9 @@
|
||||
# This workflow is intended to be run when we need to build the client and produce artifacts that require secrets
|
||||
# when the PR source branch does not have access to secrets (e.g. a fork).
|
||||
# This workflow will run in the context of the target of the PR and have access to secrets.
|
||||
# This should only be done after reviewing the PR to ensure that no malicious code has been introduced,
|
||||
# as it could allow the code on the forked branch to have access to workflow secrets.
|
||||
|
||||
name: Build Web on PR Target
|
||||
|
||||
on:
|
||||
@@ -24,7 +30,7 @@ jobs:
|
||||
uses: bitwarden/gh-actions/.github/workflows/check-run.yml@main
|
||||
|
||||
run-workflow:
|
||||
name: Run Build Web on PR Target
|
||||
name: Build Web
|
||||
needs: check-run
|
||||
if: ${{ github.event.pull_request.head.repo.full_name != github.repository }}
|
||||
uses: ./.github/workflows/build-web.yml
|
||||
|
||||
4
.github/workflows/build-web.yml
vendored
4
.github/workflows/build-web.yml
vendored
@@ -1,3 +1,7 @@
|
||||
# This workflow will run in the context of the source of the PR.
|
||||
# On a PR from a fork, the workflow will not have access to secrets, and so any parts of the build that require secrets will not run.
|
||||
# If additional artifacts are needed, the failed "build-web-target.yml" workflow held up by the check-run should be re-run.
|
||||
|
||||
name: Build Web
|
||||
|
||||
on:
|
||||
|
||||
Reference in New Issue
Block a user