Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve Continuous Delivery GHA for macOS #483

Merged
merged 1 commit into from
Jan 28, 2023
Merged

Conversation

ricoberger
Copy link
Member

The continuous delivery GitHub Action requires some secrets for the macOS build, so that the action fails for PRs from external contributors. This PR adds a check to all steps, which require some secrets to omit them for PRs where the secrets are not present, so that the action will be green.

@ricoberger ricoberger force-pushed the improve-ci-gha-for-prs branch 2 times, most recently from 7e1f522 to c5178fb Compare January 28, 2023 23:05
The continuous delivery GitHub Action requires some secrets for the
macOS build, so that the action fails for PRs from external
contributors. This PR adds a check to all steps, which require some
secrets to omit them for PRs where the secrets are not present, so that
the action will be green.
@ricoberger ricoberger added the changelog: changed Something was changed or updated label Jan 28, 2023
@ricoberger ricoberger merged commit b845844 into main Jan 28, 2023
@ricoberger ricoberger deleted the improve-ci-gha-for-prs branch January 28, 2023 23:25
ricoberger added a commit that referenced this pull request Jan 29, 2023
The change introduced in #483, caused a problem with the continuouse
delivery action when a new release is published, because the signing
steps are not executed. This should be fixed by running the necessary
steps when:

- The event name which triggers the action is "release"
- The PR is created from a branch within the repository
ricoberger added a commit that referenced this pull request Jan 29, 2023
The change introduced in #483, caused a problem with the continuouse
delivery action when a new release is published, because the signing
steps are not executed. This should be fixed by running the necessary
steps when:

- The event name which triggers the action is "release"
- The PR is created from a branch within the repository
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
changelog: changed Something was changed or updated
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant