API: repo isSecurityPolicyEnabled seems reversed (and undocumented)

[ljharb]

(i put this in "general feedback" because there's no "API feedback" category)

On a repository response, isSecurityPolicyEnabled seems to be true when the repo lacks a security policy (locally or in a .github repo), and false when it has one. This seems clearly backwards.

This field is also not documented, so we had to discover this ourselves.

Could perhaps this field be deprecated, and a new field with the correct uninverted logic be added and documented?

[ljharb]

It seems like in the last week or so, the bug was silently fixed? "true" is now reflecting that a security policy is present.

Is this property going to be documented moving forward?

[ljharb]

Looks like this field is now behaving properly and is documented.