New Failing Step Automatically added by github actions for my workflow?


I’ve started experiencing failures around 4 days ago on my webpage repo (

I have not changed my workflow at all, and the new failing step seems to have been added by GitHub to MY workflow somehow…

Here is a before screenshot:

It’s easy to see that my workflow is the last step (“Deploy to github pages with Jekyll”) after which the workflow would complete (“Complete Job”).

Starting 4 days ago this is my workflow:

As you can tell there is a new “Post Checkout” phase which I have not added and am not aware of its origins.

It is obviously failing and preventing me from completing the workflow.

The failure seems to be completely internally related to github’s own infrastructure:

##[error]error: could not lock config file .git/config: Permission denied
##[warning]An unsuccessful attempt was made using git command line to remove "http.extraheader" from the git config. Attempting to modify the git config file directly to remove the credential.
Removed matchers: 'checkout-git'
##[remove-matcher owner=checkout-git]
##[error]Access to the path '/home/runner/work/' is denied.
##[error]Exit code 1 returned from process: file name '/home/runner/runners/2.160.0/bin/Runner.PluginHost', arguments 'action "GitHub.Runner.Plugins.Repository.v1_1.CleanupTask, Runner.Plugins"'.

Googling these errors does not seem to lead me anywhere so far…

Can you try to use v1 of checkout actions instead of master?

  • uses: actions/checkout@v1

I tested in my side, v1 didn’t add post checkout step . Please let us know your result.

1 Like

Thanks! That hit the spot!