We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
You can continue the conversation there. Go to discussion →
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This feature is currently disabled: https://help.github.com/articles/about-oauth-app-access-restrictions/
It can be enabled via: https://github.com/organizations/browserify/settings/oauth_application_policy
I would do it myself, but it also eliminates SSH keys created before 2014 - of which I am not sure if any browserify infrastructure depends on.
The text was updated successfully, but these errors were encountered:
thanks for bringing this up. i think the appveyor CIs rely on this right now, not sure if there's anything else
Sorry, something went wrong.
No branches or pull requests
This feature is currently disabled:
https://help.github.com/articles/about-oauth-app-access-restrictions/
It can be enabled via:
https://github.com/organizations/browserify/settings/oauth_application_policy
I would do it myself, but it also eliminates SSH keys created before 2014 - of which I am not sure if any browserify infrastructure depends on.
The text was updated successfully, but these errors were encountered: