Maintainers should not be able to commit directly to master

[broofa]

I accidentally committed to master here. That sort of thing shouldn't be doable. master commits should only be the result of merging an approved PR.

[ctavan]

The only issue with this right now is that we‘ll have to update our version bumping and release process which currently still relies on being able to push to master.

I never got around fixing that but I would also prefer to have master protected.

While we‘re at it we could also transition from master to main for a bit more inclusive language.

[broofa]

The only issue with this right now is that we‘ll have to update our version bumping and release process which currently still relies on being able to push to master.

Ah, right, I forgot about that. Maybe set up a workflow for this that takes care of things when a new release gets tagged? (Not sure how exactly that would work)

transition from master to main

Yes, please!

[broofa]

FWIW, I just renamed master to main. It mostly seems to be working. :-)

[ctavan]

I think we should be ready to enable branch protection for admins on main once we have #636 in place as we'll no longer need the commits that npm run release currently creates on main directly.

[github-actions]

Marking as stale due to 90 days with no activity.

[github-actions]

Marking as stale due to 90 days with no activity.

[github-actions]

Closing issue due to 30 days since being marked as stale.