Skip to content
Persona 3 Dual

Git Guidelines

Guidelines for commits, PR's, and issues. Applicable to Game Dev & Web Dev teams


Commits must follow the following documentation

ResourceLinkDescription
Commit Guidelinehttps://google.github.io/eng-practices/review/developer/cl-descriptions.htmlGoogle CL Guideline

See https://google.github.io/eng-practices/review/developer/cl-descriptions.html#good
Please CAPTILIZE your commit messages!
this is incorrectThis is correct!


When you want to contribute to a repo, clone the main repo & make a branch (don’t fork the repo!).

Categorize your branches under the following sections

Branch FolderDescription
features/Feature work
tasks/Task work
bugs/Bug fixes
releases/Milestone releases
docs/Documentation changes

Ensure that the branch's name is all lowercase and follows kebab-case


Code deployment is organized into various branches. These conventions depend on the situation and the repo.

RepoBranch FolderDescription
Allmain or masterStaging deployments/latest changes
p3d-web, p3d-docsprodProduction deployments
persona-3-dualreleases/Milestone releases
Alltester/Specific tester changes

When creating a PR, the following template will appear which should be filled out accordingly.

ResourceLinkDescription
PR Templatehttps://github.com/p3d-project/.github/blob/main/PULL_REQUEST_TEMPLATE.mdOrganization-wide standardized PR template

See https://github.com/p3d-project/persona-3-dual/pull/337


https://p3dual.com/docs/onboarding/#creating-a-new-issue
TLDR: New issues must be placed in the “New” tab so that they can get reviewed first

  • Feel free to create issues anytime but keep them under New until approved
  • Only use the Feature request & Bug report templates
  • Make sure you select the correct repo to make an issue under
debug