From f7a54e5907fde4408f4984ec2ddd0ffe62204d7d Mon Sep 17 00:00:00 2001 From: Runxi Yu Date: Sat, 4 May 2024 11:50:12 +0800 Subject: A multitude of migration-related changes --- article/forge-workflows.html | 38 -------------------------------------- 1 file changed, 38 deletions(-) delete mode 100644 article/forge-workflows.html (limited to 'article/forge-workflows.html') diff --git a/article/forge-workflows.html b/article/forge-workflows.html deleted file mode 100644 index 4d842ea..0000000 --- a/article/forge-workflows.html +++ /dev/null @@ -1,38 +0,0 @@ - - - - Forge Workflows - - - - - - -

Forge Workflows

Article ID: 24

I generally use my own Git server for my projects. I also use my sr.ht account for issue tracking and mailing lists, and their Git for some projects too.

Regardless of whether I'm using my own infrastructure with plain Cgit and plain mailing lists (except that my mailing list manager is slightly broken for now), or the slightly better-integrated environment sourcehut provides, a contributor who wishes to submit some of their commits may simply do the following with git-send-email:

Configure git-send-email (only once!)
Clone the repository to a local directory
Make some changes and commit
git send-email HEAD^ --to='~runxiyu/public-inbox@lists.sr.ht' or something similar

This is much easier, imo, than the pull-request workflow popularized by GitHub (which is proprietary by the way) and similar forges:

Register an account on the forge (once per forge)
Click “fork” on the repo's Web interface
Clone the fork to a local directory
Make some changes and commit
Push
Go back to the Web interface to create a PR (which often involves clicking at least three buttons)
Delete your redundent fork once the PR is merged and your repo is not really useful anymore

Why do certain people hate on sourcehut? Really convenient workflow IMO.

- - - -- cgit 1.4.1-2-gfad0