Closed bgilbert closed 1 year ago
The repository is now under an organization, which gives us finer control over repository settings. The master branch is protected and required checks should be in place. We can further fine tune those settings if desired.
@bgilbert you also suggested renaming master
to main
(#28). Maybe now would be a good time to do that?
After required checks are enabled, individual checks need to be manually added to the required list. You'd need to search for each of the three checks in the search box, add them, then save the branch protection settings.
Renaming the branch sounds good. I don't have access to do that myself, but I think you can go ahead when ready.
(You may want to disable "require branches to be up-to-date before merging". I think it's on by default, and it can require extra rebasing that seems pointless for a project of this size.)
This setting appears to be disabled. I also added the checks.
@bgilbert let me know if you would like add further checks.
It looks like only the macOS one is marked required currently. I'd be in favor of making the Ubuntu and Windows ones required also.
Good catch. I thought it would add all three at once. All three should be required now.
After the move to ImagingDataCommons, it appears the repository configuration has changed a bit. I have some limited access to the repo settings, so I've made these changes:
I can revert any of those changes if desired.
It'd be good to enable branch protection and required checks, too, but I don't have access to do that.