Automatically alphabetise source file in an async job

[holly-cummins]

We often have to give feedback on PRs asking people to put things in alphabetical order. See, for example, #160 (comment).

We could reduce friction for contributors and effort for us if we had a CI job to sort out the order and commit back corrections.

[gastaldi]

That's a good idea

[holly-cummins]

Reminded of this by #171 (comment) :)

[gastaldi]

Instead of doing it in an async job, wouldn't be better if it performed this validation when the PR is opened?

[holly-cummins]

I think something that happened when the PR was opened could mark the PR red, but not fix the problem. So that would be a better experience for us, and faster feedback for extension authors, but we'd still be knocking their contributions back and asking them to manually do what a computer could do.

On the other hand, it avoids all the scariness of automated changes, and it would be easy to do.

[holly-cummins]

https://github.com/orgs/community/discussions/24945 seems to imply that commits can be added to someone else's PR, and provides an action for it. So maybe it is possible, in which case we should ignore all my comments above. :)

... although https://github.com/orgs/community/discussions/32032 seems to be confirming it's not possible. So maybe not.

[gsmet]

IIRC, you can push to a PR only if the PR was created from a branch of the repository itself. You won't be able to push to a forked repo.

And given you cannot have secrets in a PR, you cannot push with a PAT.