Repository navigation
Mirror every published release to Sozo-app/sozo - #79
Merged
Merged
Conversation
mirror-release.yml copies the tag (made through the API at the same commit), title, notes and files of a published release to the organization's copy. It runs on Publish, by hand, and from release.yml when that publishes or adds files itself. The copy is published only after its files are attached, so the fork's own tag-triggered release.yml skips it.
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.
When a release is published in
professorDeveloper/sozo, the same release now appears inSozo-app/sozo.What
mirror-release.ymldoesmasterhas commits of its own.…/professorDeveloper/sozo/releases/download/…point at the copy's files instead.push: tags: v*release workflow stops at its gate and builds nothing.--clobber). If the organization already has the tag at a different commit, the run stops instead of overwriting it.if: github.repository_owner == 'professorDeveloper', so the fork never copies itself.When it runs
release.ymlafter it publishes or adds files to a published release (for example aplatforms: windowsrun). WhatGITHUB_TOKENdoes starts no workflow, sorelease.ymlstarts this one itself (actions: write).Needs: the
SOZO_APP_TOKENsecret, a token that can writeSozo-app/sozo. A fine-grained token with resource owner Sozo-app and Contents: read and write is enough.Tested: the same script ran locally for sozo-tv
1.0.2and produced https://github.com/Sozo-app/sozo-tv/releases/tag/1.0.2: the tag is on commit0936a7eb, the APK is byte-for-byte the same, and the release is marked Latest. A second run updated that release instead of creating another one. The fork-side tag creation was also checked with a probe tag, which was then deleted.