Locked and Locking Issues

[Eonasdan]

Unless I missed it, there doesn't seem to be a way to filter out locked issue nor does there seem to be a way to lock an issue.

Actually, I can't find anything in the API the suggests I can do this.

Please let me know if I over looked something.

[haacked]

Hmm, I don't see it either. Perhaps @pengwynn would know.

[Eonasdan]

slightly related twbs/no-carrier#3

[pengwynn]

@haacked: Locking isn't currently available via the API. I've referenced this issue on the internal feature request for that one.

[Eonasdan]

[shiftkey]

As this is related to the GitHub product itself, rather than the API clients, I'm going to close it out.

For reference, the API is now returning locked properties for issues in Octokit (but not Pull Requests, so #1084 is that task). When the other stuff becomes available, we'll expose it in Octokit.

[haacked]

Guess what?! There's [a way to lock issues via the API now! It's in preview mode, but if someone wants to tackle it, that would be great!

[shiftkey]

The relevant docs:

• https://developer.github.com/v3/issues/#lock-an-issue
• https://developer.github.com/v3/issues/#unlock-an-issue

[cvrebert]

Finally! 😄

[prayankmathur]

@shiftkey
@cvrebert
I have added the function in the IssueClients class.
Could you please tell me what all unit and integration tests to add ?

---------EDIT----------

I have added the unit as well as the integration tests.
I cannot run the integration tests as they skip because of a lack of a test account.
The unit tests are passing fine on my system, but they seem to have a problem running on appveyor. If you could have a look and tell me what's the problem !!.
Thanks

[shiftkey]

@prayankmathur which branch is this for? If you could open a pull request it will run against our CI infrastructure - and let us see what the failures might be about...

[alexander-efremov]

@shiftkey I think this could be closed for now 👍