You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 27, 2023. It is now read-only.
I really like the look of Clippy but I can see certain people not wanting to use it on closed-source projects for fear of accidentally disclosing various aspects of their codebase. It'd be good to have a quick note about exactly what information is sent to the server (likely just a couple of GET requests with no payload... but just because you're paranoid, doesn't mean they're not after you... ;)
The text was updated successfully, but these errors were encountered:
Sounds like a good idea, maybe you could propose how that could look like (in a PR)? There's really only one request that's made, a GET to periodically retrieve the current advice
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi there,
I really like the look of Clippy but I can see certain people not wanting to use it on closed-source projects for fear of accidentally disclosing various aspects of their codebase. It'd be good to have a quick note about exactly what information is sent to the server (likely just a couple of GET requests with no payload... but just because you're paranoid, doesn't mean they're not after you... ;)
The text was updated successfully, but these errors were encountered: