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

Run your github action workflows locally to verify workflows. #33

Open
GeunjeLEE opened this issue Jun 11, 2023 · 1 comment
Open

Run your github action workflows locally to verify workflows. #33

GeunjeLEE opened this issue Jun 11, 2023 · 1 comment

Comments

@GeunjeLEE
Copy link
Contributor

GeunjeLEE commented Jun 11, 2023

AS-IS

Cloudforet maintainers sometimes develop github actions workflow for building projects.
Usually, they write workflows and verify in the cloudforet github or the test organization they own.

But, it takes a lot of effort to verify workflows.

Suggestion

Use act to write and verify github actions workflow!

Run your GitHub Actions locally! Why would you want to do this? Two reasons:

Fast Feedback - Rather than having to commit/push every time you want to test out the changes you are making to your .github/workflows/ files (or for any changes to embedded GitHub actions), you can use act to run the actions locally. The environment variables and filesystem are all configured to match what GitHub provides.

Local Task Runner - I love make. However, I also hate repeating myself. With act, you can use the GitHub Actions defined in your .github/workflows/ to replace your Makefile!

It is super simple to install and run, also provide various options (like dry-run)

Consideration

But, You should consider the following.

  1. To use a secret context locally, you need to set up an env file.
  2. Act doesn't seem to support variable contexts yet.
  3. Because maintainers must have env files for all secrets. It may lead to a security incident.
@GeunjeLEE
Copy link
Contributor Author

@piggggggggy @sulmoJ
Guys, please have a look into this issue.
It would be helpful to work.

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

No branches or pull requests

1 participant