summary refs log blame commit diff stats
path: root/forge-workflows.html
blob: 91bdcc095ed1977ea24a94e407563ddc3285d37e (plain) (tree)









































                                                                                                                                                                                                                                                                                                                                                                                                  
                










                                                                                
       
<!DOCTYPE html>
<html lang="en">
<head>
	<meta charset="UTF-8" />
	<title>Force Worlflows</title>
	<link rel="stylesheet" href="./style.css" />
	<link rel="icon" href="./favicon.ico" sizes="any" />
	<!--link rel="icon" href="./icon.svg" type="image/svg+xml" / -->
	<meta name="viewport" content="width=device-width, initial-scale=1.0" />
	<meta name="theme-color" content="#241504" />
	<meta name="color-scheme" content="light dark">

</head>
<body>
<header>
	<h1>Forge Workflows</h1>
</header>

<article>
	
	<p>I generally use <a href="https://git.runxiyu.org/">my own Git server</a> for my projects. I also use my <a href="https://sr.ht/~runxiyu">sr.ht account</a> for <a href="https://todo.sr.ht/~runxiyu">issue tracking</a> and <a href="https://lists.sr.ht/~runxiyu">mailing lists</a>, and <a href="https://git.sr.ht/~runxiyu">their Git</a> for some projects too.</p>
	<p>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 <a href="https://git-send-email.io">git-send-email</a>:</p>
	<ol>
		<li>Configure git-send-email (only once!)</li>
		<li>Clone the repository to a local directory</li>
		<li>Make some changes and commit</li>
		<li><code>git send-email HEAD^ --to='~runxiyu/public-inbox@lists.sr.ht'</code> or something similar</li>
	</ol>
	<p>This is much easier, imo, than the pull-request workflow popularized by GitHub (which is proprietary by the way) and similar forges:</p>
	<ol>
		<li>Register an account on the forge (once per forge)</li>
		<li>Click &ldquo;fork&rdquo; on the repo's Web interface</li>
		<li>Clone the fork to a local directory</li>
		<li>Make some changes and commit</li>
		<li>Push</li>
		<li>Go back to the Web interface to create a PR (which often involves clicking at least three buttons)</li>
		<li>Delete your redundant fork once the PR is merged and your repo is not really useful anymore</li>
	</ol>
	<p>Why do certain people hate on sourcehut? Really convenient workflow IMO.</p>
	<div id="footer">
		<hr />
		<p><a href="/">Runxi Yu's Website</a></p>
		
	</div>
</article>

<footer>
	<ul role="list">
		<li><a href="./">Home</a></li>
		<li>Runxi Yu</li>
		<li><a rel="license" href="./pubdom.html">Public Domain</a></li>
	</ul>
</footer>
</body>
</html>