[Module] tricky_store

[mid-kid]

ID

tricky_store

Name

Tricky Store OSS

Description

A reimplementation of Tricky Store that people can actually trust

Module repository link

https://github.com/beakthoven/TrickyStoreOSS

Source code link (for compiled binaries/APKs)

https://github.com/beakthoven/TrickyStoreOSS

Anti-Features

No response

[Atrate]

The issue author must be the owner of the module being submitted, or have permission from the owner.

@mid-kid did you contact @beakthoven before submitting this?

[mid-kid]

I didn't realize that was a requirement, didn't expect it to be. Sorry. But I guess with that ping, we now have contacted them, and we can wait for a reply.

[github-actions[bot]]

Hey @mid-kid,

your module submission was labeled with a deadline of two weeks. If you don't respond within that period, your module will be rejected.

Best regards, The MMAR Team

[beakthoven]

Regarding the module submission I would like to inform that I have no objection with Tricky Store OSS being part of the repository.

[Atrate]

Alright. As such, @mid-kid I'd like you to make a new repo that will have the contents of the TrickyStoreOSS/module directory in it (so it follows the other modules' structure). I'll add that to MMAR and make both you and beak admins of that repo.

@mid-kid since you're the one that made this submission to MMAR, you'll be responsible for making sure that the partial fork is up to date with upstream (unless beak just wants to take over this submission completely).

[ale5000-git]

Alright. As such, @mid-kid I'd like you to make a new repo that will have the contents of the TrickyStoreOSS/module directory in it (so it follows the other modules' structure). I'll add that to MMAR and make both you and beak admins of that repo.

@mid-kid since you're the one that made this submission to MMAR, you'll be responsible for making sure that the partial fork is up to date with upstream (unless beak just wants to take over this submission completely).

Personally, I found this rather limiting. Why not just using an automated workflow that on a release of the main repo just copy the content of the sub-folder in the "copied Magisk repo"?

[mid-kid]

Was gonna ask, is there any repo that does some kind of automatic mirroring using github actions, that I can use as example? If not, what do most repositories do? I'm fine with setting up a script on my machine to do it automatically, but if I can offload this to github to remedy the bus factor, I'd rather.

[Atrate]

Why not just using an automated workflow that on a release of the main repo just copy the content of the sub-folder in the "copied Magisk repo"?

Mid is free to do exactly that if they want.

[ale5000-git]

Why not just using an automated workflow that on a release of the main repo just copy the content of the sub-folder in the "copied Magisk repo"?

Mid is free to do exactly that if they want.

I have got a simpler idea that don't need to have a "real" separate repo:

1. On the main repo a workflow on every release copy the content of that folder in a "magisk" branch in the same repo.
2. The main repo is forked inside https://github.com/Magisk-Modules-Alt-Repo and in this repo the "magisk" branch is set as default.
3. The only thing needed to do manually is from time to time to trigger the "update from upstream" in the forked repo.

[Atrate]

I think this could work. I am open to trying this if you want to try @mid-kid .

[beakthoven]

3. The only thing needed to do manually is from time to time to trigger the "update from upstream" in the forked repo.

This can be pushed into a cron job with manual trigger being optional via workflow dispatch event.