Running CommandsĪnything written like this should be executed in a terminal.įor Windows this means opening the start menu and typing cmd.exe or Powershell. If you have trouble, feel free to ask in the discord or slack once you have joined. Where steps differ it will be highlighted. These steps should work for Linux, Mac or Windows. These steps will guide you to a basic setup for development. Submit pull request from your fork to master and respond to review by members.Try to ensure build passes BEFORE submitting a pull request. Push all work up into your copy of PCGen.Add tests if needed, especially if new code added. Work until the feature or bug is finished.It is good to name branches after ticket numbers, like fix_code_3444 or fix_data_3322. Create a branch in your fork of PCGen during development.Alternatively if you want to propose a new feature/change, make a JIRA entry to track it. Get a bug from JIRA primarily from the CODE or DATA sections.Programmers may want to review these if they work on the LST parsing or related systems. You can of course ask questions in the discord or slack if you are unsure. These are mainly targetted at new DATA contributors adding new books/content and fixing bugs. PCGen LST TutorialĪndrew has made a series of videos explaining the LST files. The old wiki archives historical meetings, many design documents and useful dev information.īrowse it when you have time, it can provide some insight into certain parts of the architecture.
0 Comments
Leave a Reply. |