Commit messages follow the Go project style:
the first line is prefixed with the package and a short summary. The rest of the message provides context
for the change and what it does. See
Fixes gio#nnn or
Updates gio#nnn if the change fixes or updates an existing
Contributors must agree to the developer certificate of origin,
to ensure their work is compatible with the MIT license and the UNLICENSE. Sign your commits with Signed-off-by
statements to show your agreement. The
git commit --signoff (or
-s) command signs a commit with
your name and email address.
If you have a sourcehut account, you can also fork the Gio repository, push your changes to that and use the web-based flow for emailing the patch. Start the process by clicking the “Prepare a patchset” button on the front page of your fork.
The official GitHub mirrors are open for pull requests if you prefer that workflow
git send-email setup
git send-email configured, you can clone the project and set it up for submitting your changes:
$ git clone https://git.sr.ht/~eliasnaur/gio $ cd gio $ git config sendemail.to '~firstname.lastname@example.org' $ git config sendemail.annotate yes
Include the project name in the mail subject:
$ git config format.subjectPrefix "PATCH gio"
Configure your name and email address if you have not done so already:
$ git config --global user.email "email@example.com" $ git config --global user.name "Your Name"
Whenever you want to submit your work for review, use
git send-email with the number of commit on the
current branch you want to send. For example, to submit the most recent commit use
$ git send-email -1
If you revise your patchset, add a version to the subject line with the
$ git send-email -v2 -1
Automatic patch testing
Patches with the project name “gio” in the subject will be picked up by the automatic testers at builds.sr.ht. A report with the testing results will be sent to you, CC’ed to the mailing list.