internal: add workflow to handle generating lints

[dybucc]

As mentioned in #21947.

[lnicola]

I think I'd be more comfortable going through a PR for this, but it might require additional permissions.

Also, no automated commits on Sunday evening, please.

[dybucc]

I opened a PR just for this [1], and it seemed like there was somebody (at
least) mildly interested in having lint generation automated [2]. If it's
worth merging, what schedule should the workflow run through?

[lnicola]

Any other day is fine, but releases happen Monday morning, so Sunday night is the worst possible time.

It's good to have a workflow to automate this, my point is that it would be better if the workflow opened a pull request instead of committing directly to the repo. It can be automated, but I don't know if the workflow token work for filing PRs.

[rustbot]

This PR was rebased onto a different master commit. Here's a range-diff highlighting what actually changed.

Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers.

[lnicola]

Can we try something like gh pr create --title ... --body ... --label ... instead of that action? It should be the same wrt. permissions.

[lnicola]

Actually never mind, that action has other nice features like updating an existing PR. But please pin it by hash, e.g. peter-evans/create-pull-request@c0f553fe549906ede9cf27b5156039d195d2ece0 # v8.1.0.

[lnicola]

View changes since the review

Suggested change

	uses: peter-evans/create-pull-request@c0f553fe549906ede9cf27b5156039d195d2ece0
	uses: peter-evans/create-pull-request@c0f553fe549906ede9cf27b5156039d195d2ece0 # v8.1.0

[dybucc]

Force-pushed anew to avoid having a different commit only for the comment.

[lnicola]

I suspect this won't work, but let's see.