Issue
Contribution records
Contributors

Granted credits are reviewed by maintainers. Learn more about granting credit.

Give credit to everyone
zaporylie organization(s): Unity Technologies
rrrob organization(s): Chapter Three (acquired by Kanopi Studios)
dawehner organization(s): Chapter Three (acquired by Kanopi Studios)
charly71
maximpodorov
sgurlt volunteering organization(s): Bright Solutions GmbH
jeroent organization(s): iO
danthorne
daveiano volunteering
JvE organization(s): One Shoe
klaasvw organization(s): Randstad Digital customer(s): European Commission and European Union Institutions, Agencies and Bodies
tmanhollan
mrogers
mbovan organization(s): MD Systems GmbH
anairamzap volunteering
NiCo_O organization(s): Acquia Site Studio
berdir
stevenpatz volunteering
trevorbradley
renrhaf organization(s): CGI customer(s): Ville de Montréal
aschiwi organization(s): undpaul
recrit organization(s): Phase2
el1_1el
mikemiles86 organization(s): Genuine
arsn
Git commit message
Commit types

Click on the types below to update the "Commit type" input.

  • feat: A new feature
  • fix: A bug fix
  • docs: Documentation only changes
  • style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
  • refactor: A code change that neither fixes a bug nor adds a feature
  • perf: A code change that improves performance
  • test: Adding missing tests or correcting existing tests
  • build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
  • ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
  • chore: Other changes that don't modify src or test files
  • revert: Reverts a previous commit
  • task: A planned operational or maintenance change to the codebase

See the format of the Git commit message.

Copy and paste the message in the Merge UI screen or commit message. If needed, improve the title after you paste. The message follows conventional commits format.