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 repositories custom packages.

• Press to start a new GitHub project based on this template.
  • Choose a fitting repository name and description.
  • Set the visibility to 'Public'. You can also choose 'Private' and change it later.
  • You don't need to select 'Include all branches.'
• Clone this repository locally using Git.
  • If you're unfamiliar with Git and GitHub, visit GitHub's documentation to learn more.
• Add the folder to Unity Hub and open it as a Unity Project.
• After opening the 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

• Delete the "Packages/com.vrchat.demo-template" directory or reuse it for your own package.
  • If you reuse the package, don't forget to rename it!
  • In order for the release automation to work, you should format your package name as com.username.package-name.
• Update the .gitignore file in the "Packages" directory to include your package.
  • For example, change !com.vrchat.demo-template to !com.username.package-name.
  • .gitignore files normally exclude the contents of your "Packages" directory. This .gitignore in this template show how to include the demo package. You can easily change this out for your own package name.
• Open the Unity project and work on your package's files in your favorite code editor.
• When you're ready, 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 change in release.yml:

• Change the packagePrefix to the prefix of your package. For example, if your package is com.vrchat.demo-template, the prefix is com. If your package is test.package, the prefix is test.

You will also need to modify source.json to include some important information.

• Change the instances of YOUR_GITHUB_NAME to your Github username
• Change the instances of REPO_NAME to the name of your repository

Finally, go to the "Settings" page for your repo, then choose "Pages", and look for the heading "Build and deployment". Change the "Source" dropdown from "Deploy from a branch" to "GitHub Actions".

That's it! Some other notes:

• We highly recommend you keep the existing folder structure of this template.
  • The root of the project should be a Unity project.
  • Your packages should be in the "Packages" directory.
• 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. Tags will be based on the displayname of the package and the version number, and there will be a release for every individual custom package. it wont build a release for a package if there is no change in its package.json version number.

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.