Contribution records
Contributors

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

Give credit to everyone
aohrvetpv AohRveTPV
Bakidok Bakidok
parasolx parasolx
joelpittet joelpittet organization(s): The University of British Columbia
dhruveshdtripathi DhruveshTripathi volunteering
cprajwal85 cprajwal85
gngn gngn organization(s): Computer Manufaktur GmbH
loftx2 loftx2 volunteering
megachriz megachriz organization(s): WebCoo
danchadwick DanChadwick
darkodev darko_hrgovic
mustanggb akamustang
mcdruid mcdruid organization(s): Acquia
SergFromSD SergFromSD
chegor chegor volunteering
anrikun anrikun
solideogloria solideogloria
izmeez izmeez
fabianx Fabianx volunteering organization(s): Tag1 Consulting, Inc.
richardp richardp
rob c robc
joseph.olstad joseph.olstad
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.