https://heemayl.net/enContents © 2025 <a href="mailto:me AT heemayl DOT net">Readul Hasan Chayan [Heemayl]</a> <a rel="license" href="https://creativecommons.org/licenses/by-nc-sa/4.0/" target="_blank"> <img alt="Creative Commons License BY-NC-SA" style="border-width:0; margin-top: 10px; margin-bottom: 5px;" src="https://i.creativecommons.org/l/by-nc-sa/4.0/88x31.png"></a> Tue, 21 Jan 2025 16:49:31 GMTNikola (getnikola.com)http://blogs.law.harvard.edu/tech/rsshttps://heemayl.net/posts/subshell-conditional-command-exit-status-handling/Readul Hasan Chayan [Heemayl]<div><p>Very recently, while deploying some changes via <a href="https://github.com/features/actions">GitHub Actions</a>, the pipeline was failing with this <em>ever-cryptic</em> error message:</p> <pre class="code literal-block">Error: Process completed with <span class="nb">exit</span> code <span class="m">1</span>. </pre> <p>Nothing more! Not a single hint! Which essentially meant that I would need to get down the rabbit hole myself. And I did!</p> <p><a href="https://heemayl.net/posts/subshell-conditional-command-exit-status-handling/">Read more…</a> (4 min remaining to read)</p></div>bashci/cdlinuxshellhttps://heemayl.net/posts/subshell-conditional-command-exit-status-handling/Tue, 21 Jan 2025 11:49:05 GMT