Workflow testing
Test the workflow
At this point, you shall have a working stale action.
Before going further into the customization, you may want to try it first.
Test it with the dry-run mode
Use the dry-run mode to avoid altering your repository yet.
# ...
name: Stale
id: stale
uses: sonia-corporation/stale@latest
with:
dry-run: true
You can now check the logs, and especially the statistics at the end.
You will have a better idea over what to expect when a real run without the dry-run mode occur.
Test it with a limited amount of API calls
If you still wish to play it safe, you can configure a limit of API queries calls for your issues and pull requests, and a limit of API mutations calls for your issues and pull requests to alter your repository on a reduced scope.
# ...
name: Stale
id: stale
uses: sonia-corporation/stale@latest
with:
issue-limit-api-queries-count: 30
pull-request-limit-api-queries-count: 30
Debug the action
At this point, if you have an issue, you could help yourself to save some time by enabling the debug mode of the actions by adding the ACTIONS_STEP_DEBUG GitHub secret to true in your repository.
Follow this documentation if you need more details.
You will be able to see more logs that may help you understand how the workflow is working, and also see the data fetched from your repository.
Customize the behaviour
If the action was successful, you may wish now to configure it at your convenience.
Follow the next page to have access to all the inputs.
The stale processing can be completely different between issues and pull requests.