2 ms·
git commit --allow-empty -m "bump ci" unless your pipeline does magic with trying to detect changed files
by arccy 2y ago
git commit --allow-empty -m "bump ci"
unless your pipeline does magic with trying to detect changed files
- mdaniel 2y agoIf this is to troubleshoot non-code related failures (perm issues, connection timed out, whatever influences success that doesn't require a code change) then surely the repo's history would benefit from one just clicking "Re-run Job", or its equivalent $(gh ...) invocation, right?
- arccy 2y agonot necessarily, rerun job will most likely use the fully resolved dependency graph of your actions (or equivalent), a fresh run will re-resolve them (e.g. you pinned to @1 vs the specific version like @1.2.3 of a dep). the history problem goes away if you always enforce squash merge...
- 8n4vidtmkvmk 2y agoI use Mercurial + hg-git like a weirdo. Not sure if Mercurial supports empty commits, I don't think it does.
- mdaniel 2y agoI was curious and it certainly appears that you are right $ hg init $ hg commit -m"initial" nothing changed
- 8n4vidtmkvmk 2y agoTurns out it does, actually. hg ci -m "empty commit" --config ui.allowemptycommit=1 From https://stackoverflow.com/a/71428853 https://stackoverflow.com/a/71428853. I tried it to confirm.