Skip to content

Make the warning about needing to have git in the PATH more obvious #325

Open
@yasinuslu

Description

@yasinuslu

Hi, thanks for developing this action and GitHub Actions in general, it's truly amazing.

This is more like a suggestion than an issue, I was trying to execute some git commands in the workflow and kept receiving this error:

fatal: not a git repository (or any parent up to mount point /)

I did some debugging here and there, then I finally checked out the logs of actions/checkout@v2 and saw this warning.

The repository will be downloaded using the GitHub REST API
To create a local Git repository instead, add Git 2.18 or higher to the PATH

At first it didn't occur to me that the checkout would just fetch the repository with REST API, I only thought about it after eliminating other factors. I just saw that it's mentioned in the documentation, now I'm not sure if I should create this issue or not :) It might be more helpful to make that warning more visible, let's discuss if anyone can think of a way to make it more obvious to save time for someone that might stumble upon the same issue in the future.

If you think it's obvious the way it is then we can close the issue.

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