This introduces two new flags `skip-stale-issue-message` and `skip-stale-pr-message` which would skip the message addition if these are set to true.
They are backward compatible as empty `stale-issue-message` or `stale-pr-message` will take precedence over them
Previously this action would stop and skip all issues or pull requests
it found if no `stale-issue-message | stale-pr-message` option had
been configured.
Configuring `days-before-stale: -1` will activate that behaviour.
This is to ensure we do not close issues before days-before-close has
expired. Without this fix we can encounter a situation where an issue
gets marked as stale and it gets closed immediately without waiting
days-before-close number of days.
* The bot would un-stale issues because of how it checked staleness
* Made logging info by default so its easier to troubleshoot customer issues/runs
* Updated operation counts
* Ignore issues that have recent comments and ignore the stale label. Defaulting to this behavior but added an option to turn it off.
* Fix up tests a bit to make this runnable. Add a test for the logic.
* Add vscode debugging configuration.
* Change name to isLabeled for re-use with "exempt"
* Add args for exempt labels
* Skip operation if labeled exempt
* Only check for exempt label if defined
Since the exempt label parameter is not required, we don't want to both
checking for it if it was not defined.
* Don't reduce operationsLeft if exempt
This variable just tracks the number of operations we're using to avoid
rate limiting. Since the exempt check wouldn't result in a rate-limited
request, we don't need to reduce the variable.
* Update the action.yml with new exempt values
* Update README with example of exempt labels
* Remove redundant defaults
Ross Brodbeck