My current develop-test iterations while creating a Github action is as follows:
- Develop the github action, create a release and publish it on marketplace, as v0.1.0 for instance.
- Have the sample test repository to use this action’s v0.1.0 and test the workflow
- If the action doesn’t behave as desired, push new updates on its repository, create another release and publish another version on marketplace as v0.1.1 for instance.
- Update the test repo’s workflow file to use v0.1.1 and test the workflow again
- Repeat and complain about how ineffective this is
As you can imagine, step #3 happens a lot because this is a development cycle and you may not know how to do some operations, how to pass variables, how to run steps/jobs, etc… all in advance. So you iterate tons of times when you’re creating a Github action.
Is there a way to shorten this lifecycle? Can we somehow test the actions we create, before publishing them on the marketplace and having to create version after version? This would immensely reduce the development time for your action creators.
Thank you in advance!