Putting your PowerShell code in version control is always a good idea, whether you are using a gallery or not. The added bonus of doing so is that you can integrate the code from version control into a CI system such as AppVeyor or Team Foundation Server. With the code added, every commit to your code can trigger a new build, which is immediately published to an internal or external gallery:

We will dive into those concepts when we create our own release pipeline with VSCode. For now, you can see that a CI system will be able to not only create NuGet packages from your modules, but will also be able to publish them to any gallery, be it on-premises or external. By automating these steps, you will start to build confidence in the release process and be able to quickly react to changes—applied DevOps concepts.