Directory structure for plugins on GitHub?Solved
I've been using BitBucket, but I am thinking of moving my (as of yet, not approved) mods to GitHub so I can better integrate with the site. Is there a specific structure expected for the mods, or can I point it to an individual file? The plugins are a part of a discord bot that does raid alerts and chat relay. The entire system is open source.

Is it preferrable to have a repository per file? Or a repo where all the files are in the root directory? I would rather not change what's there now, with everything together and the mods in a subdirectory of the root, but I just wanted to prepare for what's expected before moving.
Right now it requires an individual repository per plugin.
In response to Wulf ():
Right now it requires an individual repository per plugin.
Alright, thanks. :)
In response to MrPoundsign ():
Alright, thanks. :)
So I created an organization, and a repo for each plugin, but I am having an issue with figuring out how to link them all independtantly. The umod install has access to all repositories, but the install button links me to the configuration for umod on github.

Merged post

I think I got it working, in a rather round-about way. I had to uninstall umod from github, and re-add it with the install button for each plugin. Seems like perhaps it doesn't check if it's already configured / set up. It did seem to keep the configuration for all of the plugins, even though it was uninstalled and reinstalled 3 times.
You can either authorize for the entire organization or individually per repo, uninstalling each time shouldn't be necessary.
In response to Wulf ():
You can either authorize for the entire organization or individually per repo, uninstalling each tim...
It was authorized to everything; But when I went to add the integration to a plugin, I still saw the install button under the "Repository Name" section after putting in the name.
Locked automatically