Scripts and tasks for keeping MiSTer core forks synced with their upstreams.
- Setup CI/CD: Delivering CI/CD code to all forks repositories when necessary. Running on push/pull_request to this repository.
- Sync Forks: Scheduler every third hour, that cheks if the upstream has a newer release, and in that case tells the fork to sync with it.
force_fork_release.sh
: Debugging script that forces a fork release.force_forks_event.sh
: Debugging script that forces some event in this repository.merge_joydb9md_into_main.sh
: Migration script that merges branch Joy_DB9MD into master for the given fork/s.delete_branch_joydb9md.sh
: Migration script that deletes the branch Joy_DB9MD from the given fork/s.apply_replace_patch_1.sh
: Migration script that applies a replace patch to the given fork/s.delete_latest_commit.sh
: Migration script that deletes the latest commit from the given fork/s.
-
Every fork repository has to add the owner of this repository as collaborator.
-
If a fork wants to enable email notification to the maintainer in case of merge conflict or compilation error, has to add a Secret named
NOTIFICATION_API_KEY
with the proper auth key to the fork repository. -
The fork needs to appear within Forks.ini with the appropriate values in its declaration. In case it is desired to be synced it also has to be in the
SYNCING_FORKS
list.
Copyright © 2020-2021, José Manuel Barroso Galindo for the MiSTer-DB9 Team. Released under the GPL v3 License.