Version of the Action
v4.x.x
Describe the bug
When a file's line break is changed (CRLF->LF or LF->CRLF), running git status will result in an untracked modification (which passes the dirty check of this action).
However, if core.autocrlf is set to true or input, after running git add the change will be fixed and running git status or git commit after that will give you nothing to commit, working tree clean. As a result, the commit step would raise a "nothing to commit" error.
In my own case, I fixed the issue by running _switch_to_branch and _add_files before _git_is_dirty, but I'm not sure whether there will be other subsequences.
Version of the Action
v4.x.xDescribe the bug
When a file's line break is changed (CRLF->LF or LF->CRLF), running
git statuswill result in an untracked modification (which passes the dirty check of this action).However, if
core.autocrlfis set totrueorinput, after runninggit addthe change will be fixed and runninggit statusorgit commitafter that will give younothing to commit, working tree clean. As a result, the commit step would raise a "nothing to commit" error.In my own case, I fixed the issue by running
_switch_to_branchand_add_filesbefore_git_is_dirty, but I'm not sure whether there will be other subsequences.