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
check-my-repo should be a model project, clean and ready to be forked. However, since it is also used by Sauce, it is causing our results to be wrong, since parameters that should be default such as code-of-conduct are not editable. To solve this problem it is proposed that the site published at open source.saucelabs.com/check-my-repo comes from a branch instead of the main repo.
In this issue we expect to deliver 2 different results:
transform the main branch into a clean and most comprehensive repository possible to be forked
prepare a repository for Sauce Labs OSPO that will serve Sauce Labs OSPO. For that, either create nd deploy from a branch or use repolinter to check default organization documents https://github.com/saucelabs/.github
The text was updated successfully, but these errors were encountered:
Expected Behavior
check-my-repo should be a model project, clean and ready to be forked. However, since it is also used by Sauce, it is causing our results to be wrong, since parameters that should be default such as code-of-conduct are not editable. To solve this problem it is proposed that the site published at open source.saucelabs.com/check-my-repo comes from a branch instead of the main repo.
In this issue we expect to deliver 2 different results:
The text was updated successfully, but these errors were encountered: