Allow empty commits
See original GitHub issueThe feature request
Allow empty commits
Proposed solution
Do not disable the commit button when there are no changes
Additional context
Empty commits can be useful.
It allows us to start work with an empty commit and immediately open a pull request for it. In the pull request notes we are able to describe and plan to work that is going to happen on that branch before actually doing any changes.
This is possible from the command line with git commit --allow-empty -m "..."
but not with GitHub Desktop
Issue Analytics
- State:
- Created a year ago
- Reactions:4
- Comments:6 (3 by maintainers)
Top Results From Across the Web
git commit --allow-empty - Thread · house
Creating an empty commit is easy. You simply add the --allow-empty flag on git commit command and add your message. Now you can...
Read more >How to Push an Empty Commit in Git - freeCodeCamp
Git makes this process of pushing an empty commit super simple. It's like pushing a regular commit, except that you add the --allow-empty...
Read more >Pushing empty commits to remote - Stack Overflow
One use of an empty commit would be to force a build to occur in an environment where builds are triggered whenever new...
Read more >git commit --allow-empty (Example) - Coderwall
Sometimes I need to make empty commits on throw away branches so that I can trigger ... git commit --allow-empty -m "Trigger notification"....
Read more >Create an empty commit - 30 seconds of code
Use git commit --allow-empty -m <message> to create an empty commit with the provided <message> . git commit --allow-empty -m <message>. git ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
On my side I use it to create a new tag and re trigger related GitHub actions on a repository used to build a docker image. I push an empty commit when I need to rebuild the image, but I do not need to change anything in the code.
IMO, the commit button should be active even if no file is selected and trigger a confirmation modal to create an empty commit.
It would be super useful to restart CI workflows!