Issue
Contribution records
Contributors

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

Give credit to everyone
davewilly volunteering
dobe volunteering
dawehner volunteering organization(s): Chapter Three (acquired by Kanopi Studios)
Archual
benr organization(s): Studio Matris
alexpott organization(s): Chapter Three (acquired by Kanopi Studios)
ac
camilocodes
jofitz organization(s): ComputerMinds
borisson_ volunteering organization(s): Dazzle
larowlan organization(s): PreviousNext
berdir organization(s): MD Systems GmbH
jbitdrop volunteering organization(s): MAROQQO studios
jacobsanford volunteering
frankdesign
Cauliflower
joelpittet volunteering organization(s): The University of British Columbia
nicholasthompson volunteering
ksi
catch organization(s): Third and Grove
chi
lendude volunteering organization(s): iO
xjm organization(s): Acquia
quietone organization(s): PreviousNext
imanoop
fonant
nofue volunteering
manuel garcia volunteering organization(s): Appnovation customer(s): Pfizer, Inc.
raajkumar.kuru
Git commit message
Commit types
  • 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

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.