feat: create-branch=false option

[dbushong]

Fixes #151

Does not include test coverage, but adding it would mean a number of large copy-pastes or a significant refactor of src/edit-github-blob-test.ts

[mislav]

However, if you know your COMMITTER_TOKEN has permissions to bypass branch protections, it would be nice to have a create-branch: false that lets you push directly to the requested branch.

How about instead of adding a new feature, we change the logic to detect whether the committer has the ability to bypass branch protections?

This is the current logic:

bump-homebrew-formula-action/src/edit-github-blob.ts

Lines 67 to 68 in 5a3f2e9

	const needsBranch =
	inFork || branchRes.data.protected || params.makePR === true

I imagine a better condition would be something like

inFork ||
  (branchRes.data.protected && branchProtections.enforceAdmins.enabled || pushRepo.permissions.admin) ||
  params.makePR === true 

What do you think?

[dbushong]

Good thought! Seems like it doesn't work for my use case, where this is a non-admin (bot) user that's been granted permission to push directly to the relevant branch:

• pushRepo.permissions.admin === false
• branchProtections (can't fetch (because not admin?))
• branchRes.data.protected === true

I don't see a clear way in the API to detect that it's a protected branch, but OK for the currently auth'ed user (short of being admin)