Skip to content

Latest commit

 

History

History
42 lines (35 loc) · 1.27 KB

contributing.md

File metadata and controls

42 lines (35 loc) · 1.27 KB
Raw

Contributing

  1. Fork the repository to your own GitHub account.
  2. Clone your fork of the repository locally
git clone git://github.com/USERNAME/vircadia-content.git
  1. Create a new branch
git checkout -b new_branch_name
  1. Code
  • Follow the coding standard
  • Install and configure ESLINT for your editor to apply formatting for scripts
  1. Commit
  • Use well formed commit messages
  1. Update your branch
git remote add upstream https://github.com/kasenvr/vircadia-content
git pull upstream master

Resolve any conflicts that arise with this step.

  1. Push to your fork
git push origin master
  1. Submit a pull request

You can follow GitHub's guide to find out how to create a pull request. In your pull request, please include a brief test plan that can be run to validate the changes that you've made in your PR.

LFS

Certain file types in vircadia-content are tracked by Git Large File Storage (LFS) Install LFS on your development machine to ensure the following file types are tracked properly:

  • OBJ
  • FBX
  • WAV