Contribution records
Draft
Contributors

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

Give credit to everyone
bkosborne bkosborne organization(s): Princeton University
ckaotik ckaotik organization(s): werk21
alison alison
jurgenhaas jurgenhaas organization(s): LakeDrops, PARAGON Executive Services GmbH
sleitner sleitner
anon anon
damondt damondt
smustgrave smustgrave
seutje seutje
sime sime organization(s): Department of Customer Service, NSW
casey casey volunteering organization(s): SWIS
mrinalini9 mrinalini9 organization(s): Material customer(s): Drupal India Association
dbielke1986 dbielke1986
mark_fullmer markfullmer volunteering organization(s): University of Texas at Austin
boromino boromino organization(s): LakeDrops
frankdesign frankdesign organization(s): Designit
thatguy thatguy organization(s): Siili Solutions
byronveale byronveale organization(s): Princeton University customer(s): Princeton University
giordy giordy
berdir berdir organization(s): MD Systems GmbH
mrshowerman mrshowerman organization(s): BRANDCODE
steveg. steveg_git organization(s): Open Up Media
kim.pepper kimpepper organization(s): PreviousNext
alexander tallqvist AlexanderTallqvist organization(s): Siili Solutions
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.