Your repo should be cloned into Magisk-Modules-Repo, and you should receive an email to become the collaborator of that repo so you can edit it in the future.
Notes
(Windows aware!!) This git repo is configured to force Unix endlines on all necessary files. The line endings on these files should remain the Unix format. Please use advanced text editors like Sublime, Atom, Notepad++ etc. to edit the text files
In module.prop, version is any string you like, so any fancy version name (e.g. ultra-beta-v0.0.0.1) is allowed. However, versionCodeMUST be an integer. The value is used for version comparison.
Make sure your module ID doesn't contain any spaces.
(For repo developers) Magisk Manager monitors all repo's master branch. So 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 back to master.
Best Practice for Updating a Repo
Open a new branch, and start update your files on the new branch
Test if everything works fine
Bump up the versionCode in module.prop, or Magisk Manager won't know that your module is updated!
List all changes into changelog.txt, this will let users have a brief idea of your update
Merge the changes back to master, all users shall now receive the update in Magisk Manager