Repository navigation
Fix app_update submodule branch metadata - #81
Merged
wu-clan merged 1 commit intoOct 29, 2026
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Explicitly set
branch = mainfor the two community submodules added in #80:plugins/app_update→ https://github.com/SoulEater/app_update.gitplugins/app_update_ui→ https://github.com/SoulEater/app_update_ui.gitBoth repositories use
mainas their default branch. Without an explicit branch, the catalog generator falls back tomaster, so the generatedgit.branchmetadata currently points to a nonexistent branch.Scope
.gitmodules.main.Validation
Both plugin repositories' default branches were also verified via the GitHub API. This is a catalog metadata fix only, not a plugin version update.