Custom Flavor builds using SSH remotes fail

[mckraken]

Describe the bug
When using the custom flavor generator (https://megalinter.io/latest/custom-flavors/) if the repository is cloned using SSH, the megalinter action fails as git@github.com: is pre-pended when pulling the image:

Pull down action image 'ghcr.io/git@github.com:{user/org}/{repo}/megalinter-custom-flavor:latest'
  /usr/bin/docker pull ghcr.io/git@github.com:{user/org}/{repo}/megalinter-custom-flavor:latest
  invalid reference format
  Warning: Docker pull failed with exit code 1, back off 7.015 seconds before retry.

To Reproduce
Steps to reproduce the behavior:

1. Follow the steps in the referenced page, but clone it with SSH and have the git remote origin be an ssh url:

$ git remote -v
origin  git@github.com:<org>/<repo>.git

2. Go through the rest of the process. The README.md with show the following:

- GitHub Action: On MegaLinter step in .github/workflows/mega-linter.yml, define `uses: git@github.com:{user/org}/{repo}@main`

3. Even if omitting the git@github.com: from the uses: line when setting up the action, the docker pull command will still use it and present the error/failure above in the github action.

Expected behavior
That even if using SSH keys to clone a repo, the custom flavor should still work and omit the git@github.com: from the docker pull and README.md file.

Additional context

I greatly appreciate the new option to build our own custom flavors! Thank you for this option!
It's just that our standard is to use SSH for git remotes. Once I reset the repo remote origin to use HTTPS and reran the npx mega-linter-runner --custom-flavor-setup command I was able to get it to work, but it should work for SSH remotes as well.

[nvuillam]

@mckraken indeed I use git clone in HTTPS, I didn't test with SSH, we'll fix that in a future PR :)

(except if you are interested to submit the PR ? 😇 )

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity.
It will be closed in 14 days if no further activity occurs.
Thank you for your contributions.

If you think this issue should stay open, please remove the O: stale 🤖 label or comment on the issue.

[mckraken]

Commenting to keep it open. Will try to fumble through node to get a PR on this in a bit.