nix PR backporting script #26

New issue

Open

opened 2024-03-12 18:13:06 +00:00 by jade · 3 comments

jade commented

2024-03-12 18:13:06 +00:00

Owner

it should:

cherry-pick with -x to indicate commit, and use -m1 for merge commits (.... also, somehow deal with rebase/squash-merged PRs)
add an Upstream-PR: https://x line
ensure there is a change-id without requiring that people tamper with their git hooks to have a (very scuffed) pre-commit-msg hook
Do the gh api whatevers necessary to make this happen.
Possibly import the PR body since it tends to be better than the average commit message, or at least just grab both of them and let the user delete the worse one.

it should: - cherry-pick with -x to indicate commit, and use `-m1` for merge commits (.... also, somehow deal with rebase/squash-merged PRs) - add an `Upstream-PR: https://x` line - ensure there is a change-id without requiring that people tamper with their git hooks to have a (very scuffed) pre-commit-msg hook - Do the `gh api` whatevers necessary to make this happen. - Possibly import the PR body since it tends to be better than the average commit message, or at least just grab both of them and let the user delete the worse one.