v7.2.2
Minor and rare bug fix with
.lock
commands
This release fixes a rare edge case with the .lock
functionality of this Action. If users --reason <message
contained any part of the lockInfoFlag
flags, then it would think the request is for lock details, and not to claim the actual lock. This was a wacky bug but it is now resolved by just adding a single leading whitespace character to our lockInfoFlag
variable.
This release also adds enhanced debug logging for lock related functions that are internal to this Action
What's Changed
- Lock bug by @GrantBirki in #187
Full Changelog: v7.2.1...v7.2.2