From 9650a673f22b8d41242ebe937bb2fecae6b93022 Mon Sep 17 00:00:00 2001 From: Runxi Yu Date: Thu, 10 Aug 2023 00:00:00 +0000 Subject: forge-workflows.html --- article/forge-workflows.html | 37 +++++++++++++++++++++++++++++++++++++ 1 file changed, 37 insertions(+) create mode 100644 article/forge-workflows.html (limited to 'article') diff --git a/article/forge-workflows.html b/article/forge-workflows.html new file mode 100644 index 0000000..27b8e8a --- /dev/null +++ b/article/forge-workflows.html @@ -0,0 +1,37 @@ + + + + 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:

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

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. +
  2. Click “fork” on the repo's Web interface
    3. +
  3. Clone the fork to a local directory
    4. +
  4. Make some changes and commit
    5. +
  5. Push
    6. +
  6. Go back to the Web interface to create a PR (which often involves clicking at least three buttons)
    7. +
  7. Delete your redundent fork once the PR is merged and your repo is not really useful anymore
    8. +
+

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

+ + + -- cgit 1.4.1-2-gfad0