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 --- forge-workflows.html | 38 ++++++++++++++++++++++++++++++++++++++ 1 file changed, 38 insertions(+) create mode 100644 forge-workflows.html (limited to 'forge-workflows.html') diff --git a/forge-workflows.html b/forge-workflows.html new file mode 100644 index 0000000..ae2a7ab --- /dev/null +++ b/forge-workflows.html @@ -0,0 +1,38 @@ + + + + Forge Workflows + + + + + + +

Forge Workflows

+ +

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:

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

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

+
    +
  1. Register an account on the forge (once per forge)
  2. +
  3. Click “fork” on the repo's Web interface
  4. +
  5. Clone the fork to a local directory
  6. +
  7. Make some changes and commit
  8. +
  9. Push
  10. +
  11. Go back to the Web interface to create a PR (which often involves clicking at least three buttons)
  12. +
  13. Delete your redundent fork once the PR is merged and your repo is not really useful anymore
  14. +
+

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

+ + + -- cgit 1.4.1-2-gfad0 me/html/082scenario_screen.cc.html?h=hlt&id=608a7fa8d0faf9a3e3d182d9eabe969804443aab'>082scenario_screen.cc.html
blob: 13858db5e0f3c4115091b88f552329fbd5bb2b06 (plain) (tree)
1
2
3
4
5
6
7
8
9