According to the messages shown in the logs, the certificates you are using for the git clone command does not have the permissions to access the repository you want to clone.
A few days ago, it was ok
Maybe you need to check if the certificate has expired or invalid. You can try to register a new certificate to see if it can work.
- If the repository you want to clone in your workflow is hosted on GitHub, generally you can use the checkout action to checkout the repository, and use a personal access token (PAT) or the GITHUB_TOKEN to authenticate on the action:
- name: Checkout
if the repository is the one which the current workflow is running in, by default the checkout action will directly use the GITHUB_TOKEN to authenticate.
if the repository is another one, you need to create a PAT which has the permissions to access that repository and set the PAT as a secret in the repository which the current workflow is running in. Then you can use this PAT in the workflow to authenticate.
- If the repository you want to clone in your workflow is hosted on other platforms or services, you need to use the git clone command with the required certificates. The certificates can be a PAT, a SSH key or other authentications created on these platforms or services.
Before you use the certificates in your workflows or other CI services, to make sure the certificates can work for the git commands (git clone, git push, etc.), you’d better try it on your local machine at first.