[GH-ISSUE #79] CI/CD: .gitmodules with password protected repository breaks automated builds #32

Closed
opened 2026-02-26 18:45:03 +03:00 by kerem · 4 comments
Owner

Originally created by @b2cc on GitHub (Apr 15, 2023).
Original GitHub issue: https://github.com/documenso/documenso/issues/79

I recently wanted to gice Documenso a spin and configured an automated build on our Openshift cluster.
However this didn't work since the file:

references a password-protected / non-public repository.

This breaks the build since the behavior to automatically check out repos specified in .gitmodules files can't be turned off.
Would it be possible to remove this repo from .gitmodules?

Thanks for your work and support!

Originally created by @b2cc on GitHub (Apr 15, 2023). Original GitHub issue: https://github.com/documenso/documenso/issues/79 I recently wanted to gice Documenso a spin and configured an automated build on our Openshift cluster. However this didn't work since the file: * https://github.com/documenso/documenso/blob/main/.gitmodules references a password-protected / non-public repository. This breaks the build since the behavior to automatically check out repos specified in `.gitmodules` files can't be turned off. Would it be possible to remove this repo from `.gitmodules`? Thanks for your work and support!
kerem closed this issue 2026-02-26 18:45:03 +03:00
Author
Owner

@ElTimuro commented on GitHub (Apr 15, 2023):

Curious, since we are surely not the only repo doing it like this. The reference is just the project website, which is not open. Currently, there is no need to keep it there, so I just removed it.

<!-- gh-comment-id:1509921150 --> @ElTimuro commented on GitHub (Apr 15, 2023): Curious, since we are surely not the only repo doing it like this. The reference is just the project website, which is not open. Currently, there is no need to keep it there, so I just removed it. --- - Btw: There is now a developer quickstart, spinning up a local environment for getting started faster: https://github.com/documenso/documenso#developer-quickstart - Join us on Slack or create another Issue, if you have any more questions: https://join.slack.com/t/documenso/shared_invite/zt-1qwxxsvli-nDyojjt~wakhgBGl9JRl2w :)
Author
Owner

@b2cc commented on GitHub (Apr 16, 2023):

Thanks @ElTimuro !

<!-- gh-comment-id:1510437344 --> @b2cc commented on GitHub (Apr 16, 2023): Thanks @ElTimuro !
Author
Owner

@b2cc commented on GitHub (May 6, 2023):

@ElTimuro :
Just recently came back to this and there is still a reference to an unaccessible path in the git filesystem. E.g. when running git submodule update --init this still gives an error on latest main:

Cloning "https://github.com/documenso/documenso" ...
error: fatal: No url found for submodule path 'documenso' in .gitmodules

git ls-files reveals the reference which needs to be cleared:

git ls-files --stage | grep 160000
160000 8039871ab15788312715737c3d4fd0f993fea6c1 0       documenso

Could you run:

git rm documenso

to clean that up? That should do it, worked for me locally.

Reference:

All the best, and thanks again for your help and consideration!

<!-- gh-comment-id:1537112107 --> @b2cc commented on GitHub (May 6, 2023): @ElTimuro : Just recently came back to this and there is still a reference to an unaccessible path in the git filesystem. E.g. when running `git submodule update --init` this still gives an error on latest `main`: ``` Cloning "https://github.com/documenso/documenso" ... error: fatal: No url found for submodule path 'documenso' in .gitmodules ``` `git ls-files` reveals the reference which needs to be cleared: ``` git ls-files --stage | grep 160000 160000 8039871ab15788312715737c3d4fd0f993fea6c1 0 documenso ``` Could you run: ``` git rm documenso ``` to clean that up? That should do it, worked for me locally. Reference: * https://stackoverflow.com/a/4185579 All the best, and thanks again for your help and consideration!
Author
Owner

@ElTimuro commented on GitHub (May 19, 2023):

@b2cc Hey just did. Sorry, this could have happened a lot sooner, my bad 😬

<!-- gh-comment-id:1555043732 --> @ElTimuro commented on GitHub (May 19, 2023): @b2cc Hey just did. Sorry, this could have happened a lot sooner, my bad 😬
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/documenso#32
No description provided.