BUG: Actions are operating on forks with obstructive effects

GitHub Actions from https://github.com/carpentries/actions/ are operating on **forks** of https://github.com/carpentries-incubator/ and https://github.com/carpentries/ projects that results in obstructive behaviors to the commit history of users.

For example, https://github.com/carpentries/actions/blob/36232c3f437b73625c69e541ce53bfb511ba8929/record-container-version/action.yaml is not limited to particular GitHub organizations and so will run on all remotes of a https://github.com/carpentries-incubator/ project. As it has automerge behavior

https://github.com/carpentries/actions/blob/36232c3f437b73625c69e541ce53bfb511ba8929/record-container-version/action.yaml#L8-L12

any PR it opens that passes will be merged into the fork's default branch, like https://github.com/matthewfeickert/reproducible-ml-workflows/pull/2.

This then creates a divergent commit history between the fork (e.g. https://github.com/matthewfeickert/reproducible-ml-workflows/) and it's upstream (e.g. https://github.com/carpentries-incubator/reproducible-ml-workflows). This is problematic and annoying.

GitHub Actions that are going to run without user input or consent should be strictly limited to target organizations if repository level scope is not accessible (which I don't think it is).