Skip to content

Catch Gitlab HTTP error for missing submodules #29

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

Closed

Conversation

mertemba
Copy link
Contributor

Since Gitlab 17.4, for missing submodules (present in .gitmodules but not existing) Gitlab seems to report a GitlabHttpError instead of a previously raised FileNotFoundError. This is now caught.

@ValentinFrancois
Copy link
Owner

Hi, thanks for the catch!
The syntax is incorrect but I can quickly fix that.

@ValentinFrancois
Copy link
Owner

ValentinFrancois commented Jun 28, 2025

@mertemba Please have a look at #31 when you have time, this should do what you wanted (I went ahead and merged already).

@mertemba mertemba deleted the catch_gitlab_http_error branch June 29, 2025 08:07
@mertemba
Copy link
Contributor Author

Thank you for looking after this!

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