Mirror releases into the Xposed Modules Repo entry#12
Merged
Conversation
Add a workflow that mirrors each published GitHub release into the module's entry in Xposed-Modules-Repo (com.xiddoc.playintegrityalert), the source LSPosed's module browser reads from. It re-tags the mirror to the required VersionCode-VersionName shape, uploads the same APK, and syncs the entry README/SUMMARY/SOURCE_URL from the new xposed-repo/ folder — so the entry is maintained entirely from this repo while the source stays here. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UMXydF1vt9Y1NKsncTN6gd
The entry repo already exists with the user as a collaborator. Correct the setup notes: the XPOSED_REPO_TOKEN secret lives in this (source) repo, and it must be a classic PAT with public_repo scope — a fine-grained PAT can't target an org repo you only collaborate on. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UMXydF1vt9Y1NKsncTN6gd
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
2 participants
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.
What & why
LSPosed's in-app module browser reads from the Xposed Modules Repository, not from this repo — each module has a dedicated entry repo named after its package (
Xposed-Modules-Repo/com.xiddoc.playintegrityalert) that holds only a README + releases. That repository imposes rules our currentrelease.ymldoesn't satisfy on its own:VersionCode-VersionName(e.g.123-1.0.0), andThis PR keeps the source (and its human-friendly
v1.0.0release tags) here and adds a one-way mirror so the entry is maintained entirely from this repo.Changes
.github/workflows/xposed-release.yml— on every published release (and via manualworkflow_dispatch):<versionCode>-<versionName>—versionNamefrom the source tag,versionCodeas the commit count at that tag (the same valuerelease.ymlbakes into the APK);README.md/SUMMARY/SOURCE_URLfromxposed-repo/.xposed-repo/— the entry files you edit here:README.md(banner + about + usage),SUMMARY, andSOURCE_URLpointing back to this repo.Setup required (one time)
com.xiddoc.playintegrityalertentry repo and add you as a collaborator; set its repo description toPlay Integrity Alert.XPOSED_REPO_TOKENsecret to this repo — a PAT with Contents read/write on the entry repo.After that, publishing a release here mirrors it automatically.
Notes
release.ymland itsv1.0.0tags are unchanged; the compliant tag exists only on the mirror.🤖 Generated with Claude Code
Generated by Claude Code