numberq
/
foundry
1
0
Fork 0
Code Releases 1 Activity
All user data for FoundryVTT. Includes worlds, systems, modules, and any asset in the "foundryuserdata" directory. Does NOT include the FoundryVTT installation itself.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
6 Commits
1 Branch
1.7 GiB
Tree: ce57405fe2
Branches Tags
${ item.name }
Create branch ${ searchTerm }
from 'ce57405fe2'
${ noResults }
foundry/Data/systems/pf2e/CONTRIBUTING.md

40 lines
3.4 KiB
Raw Normal View History

Initial commit
1 year ago
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
 
  1. # CONTRIBUTING.md

  2. 

  3. ## Welcome All

  4. 

  5. If you would like to contribute to the project then I welcome all support. If you are (or would like to be) a developer, then hit us up on Discord (https://discord.gg/pf2e) and we can help get you up and running. Pull requests are welcome, and there are plenty of issues logged if you want to sink your teeth into something.
  6. 

  7. ## Setup

  8. 

  9. The project uses webpack to package the SASS files needed for a build and can create a local distribution for your own Foundry server. If you want to give it a go yourself follow these steps:
  10. 

  11. * Clone the repo into a local folder in your dev environment `git clone https://github.com/foundryvtt/pf2e.git`
  12. 

  13. * From within the clone's folder, Install dependencies with `npm ci`.
  14. 

  15. * You'll now need to create a symbolic link between the build folder ("dist") and your Foundry data folder. This can be done manually or by running `npm run link` and following the instructions.
  16. 

  17. * Run `npm run build` to perform a one-off build.
  18. 

  19. * Run `npm run watch` to have any coding changes you make in your dev environment trigger an automatic rebuild.
  20. 

  21. * To update compendium datafiles, run `npm run extractPacks ${compendium db filename}` after editing the item directly in the built world's compendium, rather than editing the json files directly.
  22. 

  23. ## How to Help

  24. 

  25. As a project, we are using a modified gitlab flow, with a development branch (`master`) for development and a release branch (`release`) that mirrors the development branch at a certain point in its revision history. If you want to make improvements to the project, you can ask to be added to the project or make a fork of the project in GitHub. Then push your branch to GitHub and open a pull request for your branch to our development branch. After being reviewed it can be pulled into the project by one of the project maintainers.
  26. 

  27. ### Compendium Content

  28. 

  29. As new OGL content is released by Paizo, we would like to incorporate it as soon as we are permitted (usually on a street release date). If you would like to contribute such content, please keep in mind the following guidelines:
  30. * Name the entities (be they physical items, abilities, or other discrete game features) exactly as they are in the source material, with one exception: square brackets (`[` and `]`) should replaced with another set of characters, like parentheses, or simply omitted.
  31. * Any embedded links to other entities should be of the form `@Compendium[pf2e.pack-name.Entity Name]`. For ease of maintenance, the linked entities should be referenced by *name* rather than by ID.
  32. * Do not submit new graphics (especially copyrighted graphics) without first receiving clearance from the copyright holders, if applicable, as well as this repository's maintainers.
  33. 

  34. ### Pull Requests

  35. 

  36. Pull requests ("PRs") can be made by anyone. PRs titles should be in imperative mood and state clearly and concisely what is being changed. A description is often needed to expand on any details. For new contributors, CI actions must be manually triggered by the system maintainers. It will automatically trigger for subsequent pull requests after a first one is merged into `master`.
  37. 

  38. #### Prettier

  39. 

  40. We have integrated [Prettier](https://prettier.io/) into this project to enforce a consistent coding—even if it's not one everybody likes. Github CI will block merges of any PR that fails the test suite, which includes style linting. To manually fix style issues, you can call `npm run lint:fix` from the project environment.