-
Notifications
You must be signed in to change notification settings - Fork 216
Lock issue #480
Comments
@Nowaker Could you send a PR for this? I am working on the backlog and it will be a while before I will be able to get to this. Sounds like a cool feature 😄 |
Looks like this can be done cleanly with the newly add octokit api: https://octokit.github.io/rest.js/#octokit-routes-issues-lock File location to add this would be here: Line 118 in 8b772f1
The approach would be to add a new flag like And do |
This feature will allow you to lock issues and provide the reason for locking. re node-gh#480
Allows for locking an issue and or adding a lock reason. re node-gh#480
Allows for locking an issue and or adding a lock reason. re node-gh#480
@protoEvangelion I guess it would had met my need two years ago for sure. That need is long gone with the project I was working on. But still thanks, someone else will find a use for it, yay! 😀 |
Ha sorry it took so long! |
Allows for locking an issue and or adding a lock reason. re #480
# [2.8.0](v2.7.1...v2.8.0) (2019-11-13) ### Features * **issue:** add issue locking capability ([b9b8994](b9b8994)), closes [#480](#480)
🎉 This PR is included in version 2.8.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Something like
gh is 123 --lock
The text was updated successfully, but these errors were encountered: