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

improve documentation for integrating with GitLab CI #462

Merged
merged 1 commit into from May 2, 2024

Conversation

webit-richardkramer
Copy link
Contributor

When implementing pronto in our GitLab CI we ran into an issue when having more than 50 commits in an MR. In this case, pronto simply showed all issues, not only the ones in our changes.

The cause of this was GitLabs git depth (50 by default for us, 20 on newer installations). Unfortunately, it is not enough to separately fetch the target branch (which was already present in the docs), but also to refetch the history of HEAD beyond the initial fetch depth.
You could also do this explicitely, by I found it cleaner to simply disable the git depth for this one job.

In case others stumble upon the same problem, I want to update the docs a bit to reflect this need of disabling git depth.

@webit-richardkramer webit-richardkramer requested a review from a team as a code owner April 29, 2024 05:57
@ashkulz ashkulz merged commit 0e33c4b into prontolabs:master May 2, 2024
11 checks passed
@ashkulz
Copy link
Member

ashkulz commented May 2, 2024

Thanks for the contribution, @webit-richardkramer!

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.

None yet

2 participants