Workflows to be public for free and open source projects
C
Chris Withers
If I visit https://circleci.com/gh/cjw296/workflows/playground/tree/master when not logged in, I get a partially rendered page with no content.
If I visit https://circleci.com/workflow-run/1f24ce13-8835-478d-a612-fc713dd100d8 when not logged in, I get a 404.
This is a public, open source project and I'd expect people who haven't logged in to CircleCI to still be able to view workflows and their results...
Looks like other people have hit this too and feel it might even be classed as a bug:
This likely has a lot of overlap with https://ideas.circleci.com/ideas/CCI-I-569.
Why might CircleCI want to do this? Well, it's a lot easier for me to sell CircleCI for commercial use to people when they don't have to log in to see some sample output!
CCI-I-903
Jean-Paul Calderone
Please implement this. A public, free, open-source project may have many contributors and it may not be feasible or desirable for them to all register with CircleCI. This means that a public, free, open-source project currently has a reason to
avoid
CircleCI because using CircleCI will exclude some people from contributing who could otherwise contribute.Richard Všianský
We had the same issue on https://github.com/data-driven-forms/react-forms
As an open source project we need to show our community members why their PRs fail - lint errors, wrong builds, failed tests. And we understand that not everyone wants to use their private accounts to log in to external services.
R
Radon Neon
Yes, I consider this a bug. Contributors to my open-source projects are unable to view logs because they (reasonably) do not want to grant read/write access to all of their repositories. See e.g. https://github.com/raxod502/selectrum/pull/201#issuecomment-695949107. There is at least a workaround, which is to create a separate GitHub account just to authorize CircleCI, but that's pretty unprofessional.
(1) authentication should not be required, what's the point of "public" otherwise
(2) even if it is, no additional OAuth scopes beyond identity should be requested, since they're clearly not needed
J
Joeldenning Circleci
I'd love this, too