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
GitHub blocks google from indexing via robots.txt. This means that google knows about the Secure Coding guide for Python but does not read up its content. So a search would have this page result in an empty content.
Not sure how to solve this other then getting the section published on openssf.org.
The text was updated successfully, but these errors were encountered:
We generally haven't been sharing that link. It was my understanding that the Python guide wasn't ready for widespread use. If you think it's ready, please bring that proposal to the Best Practices WG for release, so we can get the word out.
There's no robots.txt file for best.openssf.org (we could make one, if we want to). So Google will index it just fine.
If you want to use the best.openssf.org link everywhere so it's linked, I can see the argument for that. In that case, I think it's important that the guide indicate it's a "draft" until it isn't. That might be a good idea anyway :-).
GitHub blocks google from indexing via robots.txt. This means that google knows about the Secure Coding guide for Python but does not read up its content. So a search would have this page result in an empty content.
Not sure how to solve this other then getting the section published on openssf.org.
The text was updated successfully, but these errors were encountered: