You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I am attempting to use the new commit arguments option to create an empty commit by passing in '--allow-empty'. The logs show that it is correctly evaluated as an input. The precise commit command does not seem to be printed by even detailed debug logs, but the internal logs show the normal 'Working tree clean. Nothing to commit.' message, indicating the argument was not executed.
::set-output name=tagged::false
##[debug]='false'
Running in /home/runner/work/taskchain/taskchain
##[debug]Input parsed as single string
Add input parsed as single string, running 1 git add command.
Using 'mcargille mcargille@users.noreply.github.com' as author.
##[debug]Committer: mcargille mcargille@users.noreply.github.com
Using "closes #16" as commit message.
##[debug]Current push option: 'true' (parsed as boolean)
::group::Internal logs
Internal logs
Staging files...
Adding files...
##[debug]Input parsed as single string
##[debug]Git args parsed:
##[debug] - Original: .
##[debug] - Parsed: ["."]
No files to remove.
Checking for uncommitted changes in the git working tree...
::endgroup::
Working tree clean. Nothing to commit.
::group::Outputs
Outputs
committed: false
commit_long_sha: undefined
commit_sha: undefined
pushed: false
tagged: false
::endgroup::
##[debug]Node Action run completed with exit code 0
##[debug]Finishing: Run EndBug/add-and-commit@v8.0.0
The text was updated successfully, but these errors were encountered:
Looks like there's an explicit check in code that the working tree is not empty, reasonably assuming that no one would be wanting to intentionally allow empty commits.
Hi, thanks for opening the issue!
Yeah, I totally assumed that no one would ever need to create an empty commit 😅
I don't want to allow empty commits by default, since I don't want the action to fail in that case, so I guess I could check whether the commit input contains the allow-empty option 👍🏻
Describe the bug
I am attempting to use the new commit arguments option to create an empty commit by passing in '--allow-empty'. The logs show that it is correctly evaluated as an input. The precise commit command does not seem to be printed by even detailed debug logs, but the internal logs show the normal 'Working tree clean. Nothing to commit.' message, indicating the argument was not executed.
Workflow used
Expected behavior
Expected the 'commit: --allow-empty' option to be passed to the commit command and successfully create an empty commit.
Logs
The text was updated successfully, but these errors were encountered: