Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: add troubleshooting #1

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Conversation

dgoosens
Copy link

@dgoosens dgoosens commented Feb 13, 2024

Added troubleshooting info about Failed to push your source code because your repository is shallow and therefore cannot be pushed to the Clever Cloud remote error message on GitLab
This section explains how to setup GitLab to avoid this issue

And added troubleshooting message about Application not found error
This requires one adds the info about the organization with the --org param

Added troubleshooting info about `Failed to push your source code because your repository is shallow and therefore cannot be pushed to the Clever Cloud remote` error message on GitLab
@dgoosens dgoosens changed the title chore: add troubleshooting about shallow clone chore: add troubleshooting Feb 13, 2024
chore: added troubleshooting message about `Application not found` error
Copy link
Collaborator

@juliamrch juliamrch left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @dgoosens I'm updating this repo with new scripts that should resolve this PR and avoid a troubleshooting section. Let me know what you think of this if you have some time.

Sorry for taking so long to respond, you can ping me on any PR or issue so I get the notification 🙏

Solution is to make sure one has a full copy of the repository.
To do so, in GitLab, go to `Settings` > `CI/CD` > `General pipelines` and scroll to the `Git strategy` section.
There either choose `git clone` to have a full clone of the repository or use `git fetch` but set `Git shallow clone` to `0` to make sure you get the full history

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @dgoosens, thanks for the PR!

I've opted to add to the scripts the following line:

variables:
 GIT_DEPTH: 0

This prevents the error and avoids getting the user too much into GitLab documentation, to get started and running asap.

This may mean you need to specify the organization aswell

```bash
clever link ${APP_ID} --org ${ORG_ID}
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Have you encountered this error? Because it arises when you try to link using the alias, but not with the app_id which is linked to the organisation by default.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants