Skip to content

fix: update Dependabot path for gitsubmodule (#452)#453

Open
lubianat wants to merge 1 commit intoome:mainfrom
lubianat:patch-1
Open

fix: update Dependabot path for gitsubmodule (#452)#453
lubianat wants to merge 1 commit intoome:mainfrom
lubianat:patch-1

Conversation

@lubianat
Copy link
Contributor

Related to #449, fixes #452

This assumes that we want Dependabot to track all submodules (not only dev, but also previous versions).

It will look into .gitmodules for the updates (which is in /, and not in /specifications/dev).

My experience with Dependabot is limited, though, so I might be overlooking something.

Assumes intent is to track all submodules.
@lubianat lubianat requested a review from jo-mueller February 26, 2026 15:10
@github-actions
Copy link
Contributor

Automated Review URLs

@jo-mueller
Copy link
Contributor

My original idea was to keep the dependabot pointed only at the dev submodule by choice, because it's the only continuously developing submodule and I wouldn't expect any changes on the other branches in the future.

That being said, it would be cleaner if we put out releases from the 0.1...0.5 branches and then point the submodules to the releases rather than just the branches.

@lubianat
Copy link
Contributor Author

I see! We can exclude the others, but I imahine that if eventually we change an older branch (say, to fix a broken link or similar), it may be good for the dependabot to trigger a PR here.

If they are not changed, then dependsbot will just stay silent, right?

Are there scenarios in which we would not want an update to be propagated here?

But either way works for me

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.

dependabot issue from #449

2 participants