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

working workflow, individually check for the existence of secrets #191

Merged
merged 3 commits into from
May 11, 2022
Merged

Conversation

leonhma
Copy link
Contributor

@leonhma leonhma commented May 11, 2022

Hi it's me again. I modified the workflow to check for the existence of the required secrets (CHROMATIC_PROJECT_TOKEN and FOSSA_API_KEY), so that these steps don't run when no token is configured. This way it makes much more sense than just disabling the workflow for pull requests, since then forked repos would have had to add their tokens or have the workflow immediately fail.
This is meant to be a drop-in replacement, since the secrets are already configured. Basically just 'merge/rebase' and that's it.

PS: The solution to testing for secrets is a bit hacky, github actions doesn't have anything nicer.
PS2: The fetch-depth: 0 can be removed, we don't need the entire repo (currently it takes a whole minute to download the repo). We only need the latest code (commit).

@mauriciopoppe mauriciopoppe merged commit 5a7f4ce into mauriciopoppe:master May 11, 2022
@mauriciopoppe
Copy link
Owner

lgtm, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants