Recommended way to create a Dev/test environment for CI related contributions

Hi I am new to Github Actions and Meshery both.

What is the recommended way of creating a Dev/Test environments for testing changed to Github Actions on our personal forks?

This also includes setting up tokens and/or other secrets

Any tips or resources will be appreciated!

I’ve never had much luck with GitHub - nektos/act: Run your GitHub Actions locally 🚀. @DelusionalOptimist, any suggestions?

1 Like

@hershd23 as Lee pointed out, nektos/act exists but even I haven’t had much success with it. It is also inconvenient when you use it with GH actions that depend on Minikube or Kind as Kubernetes clusters, which themselves depend on docker.

My personal workflow goes like: fork the action’s repo, make your branch, keep doing your changes and pushing them to your branch. For testing your changes, you can either make a workflow in the fork itself which uses your action and runs on every commit you push or you can have a separate repo for testing where you’ll create a workflow referencing your action and trigger it manually each time you want to test your changes.

A small guide on getting a token and using the meshery-smp-action in your CI/CD pipelines: Performance Management with Meshery | Meshery
Another guide for using the mesheryctl-smi-conformance-action: Running SMI Conformance Tests | Meshery
For using secrets in workflows, I’ve found the official docs to be very helpful:
Encrypted secrets - GitHub Docs.

1 Like

Hey thanks @DelusionalOptimist. Your answer is pretty comprehensive, marking it as the solution

1 Like