Pull Requests via Git Push
Steinar H. Gunderson introduced a new method on git.sesse.net, enabling pull requests via git push through email. This simplifies patch submissions, despite limitations like no multipush support and potential errors. Security measures are highlighted.
Read original article
Steinar H. Gunderson shared a new approach on July 15, 2024, regarding pull requests via git push on git.sesse.net. By allowing git push to create pull requests via email, contributors can now submit patches more easily without relying on custom SSH-facing code. The process involves setting up a pre-receive hook to handle incoming pushes, which triggers an email with the patch for review. This method simplifies the contribution process, although it has limitations like no support for multipush and potential errors when pushing to non-existing branches. Despite drawbacks such as limited spam control and fixed committer email, this system enables seamless patch submission for review and potential inclusion. Steinar H. Gunderson emphasizes the security measures in place to address any potential vulnerabilities.
Related
I kind of like rebasing
People debate Git workflows, favoring rebasing for a linear history. Redowan Delowar prefers rebasing to consolidate changes and maintain a clean commit history. They discuss interactive rebasing benefits, squashing commits, handling conflicts, and offer practical tips.
Git-PR: patch requests over SSH
A new git collaboration service, git-pr, simplifies self-hosting git servers via SSH. It combines mailing list and pull request workflows, streamlining code collaboration. Users interact in the terminal, enhancing code review with patch requests. Notifications via RSS feeds and state changes reflected in static web assets. The service aims to bridge pull requests and email-based collaboration efficiently.
3 commentsUsing --from with git-format-patch will add the From: header to the commit message body in the standard way when emailing a patch written by someone else, which would allow you to preserve this easily without risking excitement from injection attacks into email headers.
Maybe the right behaviour for all-zero $oldsha is to quietly turn format-patch $oldsha..$newsha into format-patch --root $newsha?
echo 'The push will now exit with an error. No commits have actually been pushed.'
Related
I kind of like rebasing
People debate Git workflows, favoring rebasing for a linear history. Redowan Delowar prefers rebasing to consolidate changes and maintain a clean commit history. They discuss interactive rebasing benefits, squashing commits, handling conflicts, and offer practical tips.
Git-PR: patch requests over SSH
A new git collaboration service, git-pr, simplifies self-hosting git servers via SSH. It combines mailing list and pull request workflows, streamlining code collaboration. Users interact in the terminal, enhancing code review with patch requests. Notifications via RSS feeds and state changes reflected in static web assets. The service aims to bridge pull requests and email-based collaboration efficiently.