We need an HTTP token per project GITLAB_TOKEN. I used to use the same token for Silkaj and DunitePy. Now, we have to have to set the token when working on one or the other project. Since there is no custom env variable. May be it’s not a big deal, if we are changing gitlab-ci.yml, we set the token, get it checked before pushing. Probably GitLab v16 API change related (not the tool it-self). Upstream can support to read different env variable names.
They are determining the GitLab instance with git remote -v. I had g1_monetary_license remote in my Silkaj local clone for the Ğ1 Monetary License subtree. Therefore, the check was failing, because it was running on the wrong project, token are projects specific now. I can delete this remote. But, having GitLab URL hardcoded is somehow safer. The tool should support to hardcode an URL as https://gitlab.com/devopshq/gitlab-ci-linter/ does. I found that adding grep origin solves the issue.
These topics can be reported and fixed upstream for better support.
In the meantime, this hook seems to be the only one supporting GitLab v16, so let switch to it even though there are known limitations.
In the end I managed to have gitlab-ci-linter working as stated in #4 by specifying --project client/python/$project. I didn’t manage to have it working last time probably because I was using DuniterPy token on Silkaj project as stated in first bullet point above.