Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Post History
Based on the SO comments, this is not a good general practice, and I believe the point of the posts mentioned in the question is that it can be done (but one probably shouldn't) this can be use...
Answer
#1: Initial revision
by
toraritte
·
2023-11-08T13:39:30Z (6 months ago)
Based on the [SO comments](https://stackoverflow.com/questions/68440032/what-is-the-point-of-triggering-ci-cd-with-an-empty-git-commit), this is not a good general practice, and I believe the point of the posts mentioned in the question is that + it can be done (but one probably shouldn't) + this can be used to test a CI/CD build service/system without having to add a contrived change. It seems that a good general rule would be to push empty commits only to personal work branches, and remove them before a pull request and/or merging to `master`/`main`. --- The SO thread [Pushing empty commits to remote][4] asks questions (see below) that would answer this thread, but they have been completely ignored there. > Are there any disadvantages/consequences of pushing empty commits? Is there any problem I might face in future because of this empty commit?? --- Apparently, there is also the practice of [starting a repo with an empty commit](https://web.archive.org/web/20170919074934/http://bit-booster.com:80/doing-git-wrong/2017/01/02/git-init-empty/). Read the post a couple of times, but still don't understand the reasoning (and I suspect that it is perhaps a satirical post). [4]: https://stackoverflow.com/questions/20138640/pushing-empty-commits-to-remote