- Fork this repo
- Edit "config.sh", and follow the instructions in the script file to create your own Magisk Module. Note that you might want to use Notepad++ on Windows, since the script files are using Unix endline.
- Edit "module.prop" with the manifest of your module
- Edit "changelog.txt", the info will be shown in Magisk Manager
- Edit the description of your Github repo to the ID of the module. Magisk Manager uses that value as identification
- Contact @topjohnwu on XDA for a request to add a new module repo. You'll get an empty repo with permission only given to you and the owners of Magisk-Modules-Repo.
- Push your module to the new repo created for you. You can push updates directly to your repo in the future as you wish.
- In the module.prop file, version is any string you like, any fancy version name (e.g. ultra-beta-v0.0.0.1) is allowed. However, the versionCode "MUST" be an integer. The value is used for version comparison.
- Make sure the ID in module.prop doesn't contain any spaces.
- Any changes to the branch "master" will be reflected to all users immediately. If you are working on an update for a module, please work on another branch, make sure it works, and then merge the changes to master.
- Open a new branch, and start working on it
- Test if everything works
- Bump up the versionCode in module.prop, or Magisk Manager won't know that your module is updated!
- Edit changelog.txt with the changes you made
- Merge the changes to master, all users will now receive the update in Magisk Manager