Contribution records
Draft
Contributors

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

Give credit to everyone
dmsmidt MrDamasajaga organization(s): Triquanta
nitebreed Nitebreed organization(s): Synetic
ericmulder1980 ericmulder1980 volunteering
krilo_89 Krilo_89 organization(s): Synetic
berdir berdir organization(s): MD Systems GmbH
mpdonadio matthew.donadio organization(s): DiD Agency
johnchque yongt9412 organization(s): MD Systems GmbH
mgifford mgifford organization(s): CivicActions, OpenConcept Consulting Inc.
jhedstrom jhedstrom organization(s): Phase2 customer(s): Human Rights Watch
ankusht1515 ankusht1515 organization(s): Material customer(s): Drupal India Association
luke.leber lleber volunteering
ssawafta ssawafta
kentr kentr volunteering
ali izzeldin ali_izzeldin
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.