Preview mode

[ossf]

Preview mode

[jeffmendoza]

Yes, I completely agree that this is a top issue to solve. Currently, I'm not sure of how it could work. We don't want to post the preview data publicly without some configuration action by the org-owner. A long-term solution could be a private portal that you log into with your GitHub credentials, and Allstar only shows you the results that you own. That would take some time to build.

A quicker hack that has come to me when thinking about this now is to create a single issue on the .allstar repo with the results of a preview. How does that sound to you? Any suggestions? Thanks!

[jeffmendoza]

Another thing: without preview mode a good way to slowly enable might be:

First use opt-in mode and explicitly list your important and active repos.

Next, after that goes well, switch to opt-out mode and opt-out a list of your old / stale repos that you wouldn't fix to avoid opening unnecessary issues on those. (Though I'd consider archiving those repos as well). With this config Allstar would be enabled on newly-created repos by default.

[Hixie]

A single issue in the .allstar repo would work great. That would also be a sufficient work-around for #59 for now.

[jeffmendoza]

Sounds good, I'll write up a proposal.

[Hixie]

One thing that would be valuable is if this preview did not report problems in archived repos. I mention this only because the logs you kindly provided me for flutter do include things like "this repo doesn't have branch protection" for repos that are actually archived and thus don't need branch protection (because they have the ultimate protection, heh).