Developing modules

Note

Always start from main, but never commit to main.

Let’s say you want to make changes to our Fun repository.

If you were to use repository install command, the bot would place it into the modules/ directory. That’s where you have to clone your fork as well, so the bot can find and load it.

cd modules/
git clone git@github.com:<your username>/pumpkin-fun.git fun

Make sure you name the cloned directory correctly (e.g. the fun argument in the command above): it has to be the same as the name in repository’s repo.conf. An example of such a file is just below:

[repository]
name = fun
modules =
    dhash
    fun
    macro
    rand

Now you can start your bot. You should see that their database tables have been created. All these modules should be showing up now when you run repository list.

Now you can make branches, commit changes and open PRs back into the main repository as usual.