Error: Command failed: git config --get remote.origin.url

[DavidGOrtega]

Non cloud self-hosted runners might suffer from Git dependency.

Error: Command failed: git config --get remote.origin.url
    at checkExecSyncError (child_process.js:635:11)
    at execSync (child_process.js:671:15)
    at gitRemoteUrl (/usr/lib/node_modules/@dvcorg/cml/src/cml.js:32:15)
    at new CML (/usr/lib/node_modules/@dvcorg/cml/src/cml.js:77:44)
    at run (/usr/lib/node_modules/@dvcorg/cml/bin/cml-send-comment.js:14:15) {
  status: 1,
  signal: null,
  output: [ null, <Buffer >, <Buffer > ],
  pid: 38581,
  stdout: <Buffer >,
  stderr: <Buffer >
}

[0x2b3bfa0]

Yes, all the CML commands require the git command-line tool to be present in order to infer the repository address; this shouldn't change. However, we should let users invoke commands with --repo if the inferrence is not possible.

[0x2b3bfa0]

Possible workarounds:

• Show a descriptive error message when running commands that need to infer the repository address by running the git command, so users can decide to install git or use the --repo option. See Handle environments without Git with a helpful error message #628 for a sample patch.

• Use $GITHUB_SERVER_URL/$GITHUB_REPOSITORY on GitHub and $CI_PROJECT_URL on GitLab to determine the gitRemoteUrl without having to rely on external tools. This would not work outside the supported CI/CD environments.

• Use a JavaScript Git implementation as @DavidGOrtega suggested and keep relying on Git to detect the repository address.

[dacbd]

Barring the merge of #1003
also with https://cml.dev/doc/ref#--repo being present now I think its safe to close this.

[casperdcl]

Do we need to action some things though?

• update some FAQ in the docs?
• improve the CLI error message Add documentation links and helpful descriptions to error messages #606?
• fix & merge No native git dependency #1003?