Conducting research is hard, the platform you use shouldn’t be. Help improve the registration process on OSF by completing a brief 10-minute study at any time that works for you. 📄 Instructions: bit.ly/3GZZvRg 👉 Take the study: bit.ly/3wdQZc2

Over the next 72 hours, OSF user support is transitioning to a new platform, including a new help guide center & improved customer communications. Thank you for your patience during this transition. If you experience delays from OSF support, please reach out to contact@cos.io.

Hi, EJ. This question came up in one of our webinars: piped.video/watch?v=CspRk3hB…. We don't see any reason to withhold it either, though we still need to implement it. You will see this option available shortly for OSF content, and hosted services that choose to make it available.

You shouldn't need to use the robots.txt as that's just for the MFR which no one really uses. Try:

The default branch for a connected GitHub repo is set to Master, but you can select different branches within a repo to view within your file tree (there just isn't a way to set a different branch as your default). See attached screenshot for details. I hope this helps!

@_r_c_a this is expected behavior as anyone can find public content at any time. In this way, VOLs are meant for private projects. In order to make it harder for reviewers to find the nested public component, you should NOT associate the components with the parent VOL.