Skip to content

Enable debug/verbose logging to diagnose failures of fetching the repository #1713

Open
@matusnovak

Description

@matusnovak

I have a problem that in my private repo the fetching step fails, but I could not find any way to diagnose the problem.

Such output looks like this:

Fetching the repository
  /usr/bin/git -c protocol.version=2 fetch --no-tags --prune --no-recurse-submodules --depth=1 origin +refs/heads/403/merge*:refs/remotes/origin/403/merge* +refs/tags/403/merge*:refs/tags/403/merge*
  The process '/usr/bin/git' failed with exit code 1
  Waiting 20 seconds before trying again
  /usr/bin/git -c protocol.version=2 fetch --no-tags --prune --no-recurse-submodules --depth=1 origin +refs/heads/403/merge*:refs/remotes/origin/403/merge* +refs/tags/403/merge*:refs/tags/403/merge*
  The process '/usr/bin/git' failed with exit code 1
  Waiting 11 seconds before trying again
  /usr/bin/git -c protocol.version=2 fetch --no-tags --prune --no-recurse-submodules --depth=1 origin +refs/heads/403/merge*:refs/remotes/origin/403/merge* +refs/tags/403/merge*:refs/tags/403/merge*
Error: The process '/usr/bin/git' failed with exit code 1

Which is not helpful.

Is there any way how I can enable debug or verbose logging for actions/checkout, so that I could diagnose the problem on why the git command failed?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions