@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.