Starter for making Packages, including automation for building and publishing them.
Once you're all set up, you'll be able to push changes to this repository and have .zip and .unitypackage versions automatically generated, and a listing made which works in the VPM for delivering updates for this package. Multi-package repo support is yet to come.
- Press
to start a new GitHub project based on this template, and follow the directions there. - Clone this repository locally using git.
- Open the folder as a Unity Project.
- Wait while the VPM resolver is downloaded and added to your project. This gives you access to the VPM Package Maker and Package Resolver tools.
- Full details at Converting Assets to a VPM Package
You can delete the "Packages/com.vrchat.demo-template" directory or reuse it for your own package.
Update the .gitignore file in the "Packages" directory to include your package. It has an example of including the demo package which you can easily change out for your own package name.
You can open the Unity project and work on your package's files in your favorite Code Editor. Then commit and push your changes. Once you've set up the automation as described below, you can easily publish new versions.
You'll need to make a few changes in release.yml:
- Changed the
pathsproperty on line 7 to point to the directory where your Package's source files are. Leave the/**at the end so GitHub knows to run this action whenever any file in that directory is changed. In the example, this property reads:paths: Packages/com.vrchat.demo-template/** - Change the
packageNameproperty on line 10 to include the name of your package, likepackageName: "com.vrchat.demo-template" - We highly recommend you keep the existing folder structure where the root of the project is a Unity Repo, and your packages are in the "Packages" directory, If you change this, you'll need to update the paths that assume your package is in the "Packages" directory, on lines 24, 38, 41 and 57.
That's it. If you want to store and generate your web files in a folder other than "Website" in the root, you can change the listPublicDirectory item here in build-listing.yml.
A release will be automatically built whenever you push changes to your main branch which update files in the package folder you specified in release.yml. The version specified in your package.json file will be used to define the version of the release.
Whenever you make a change to a release - automatically publishing it, or manually creating, editing or deleting one, the Build Repo Listing action will make a new index of all the releases available, and publish them as a website hosted fore free on GitHub Pages. This listing can be used by the VPM to keep your package up to date, and the generated index page can serve as a simple landing page with info for your package. The URL for your package will be in the format https://username.github.io/repo-name.
The action which rebuilds the listing also publishes a landing page. The source for this page is in Website/index.html. The automation system uses Scriban to fill in the objects like {{ this }} with information from the latest release's manifest, so it will stay up-to-date with the name, id and description that you provide there. You are welcome to modify this page however you want - just use the existing {{ template.objects }} to fill in that info wherever you like. The entire contents of your "Website" folder are published to your GitHub Page each time.
You are welcome to make your own changes to the automation process to make it fit your needs, and you can create Pull Requests if you have some changes you think we should adopt. Here's some more info on the included automation:
This is a composite action combining a variety of existing GitHub Actions and some shell commands to create both a .zip of your Package and a .unitypackage. It creates a release which is named for the version in the package.json file found in your target Package, and publishes the zip, the unitypackage and the package.json file to this release.
This is a composite action which builds a vpm-compatible Repo Listing based on the releases you've created. In order to find all your releases and combine them into a listing, it checks out another repository which has a Nuke project which includes the VPM core lib to have access to its types and methods. This project will be expanded to include more functionality in the future - for now, the action just calls its BuildRepoListing target.
