Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
sam152
timmillwood organization(s): Appnovation customer(s): Pfizer, Inc.
jhedstrom organization(s): Phase2 customer(s): Workday, Inc.
bojanz organization(s): Centarro
tacituseu
amateescu customer(s): Pfizer, Inc.
xjm organization(s): Acquia, xjm
nigelcunningham organization(s): Grindstone Creative
marcoscano organization(s): Lullabot
jonathanshaw
alexpott
energee volunteering
berdir organization(s): MD Systems GmbH
anchal_gupta organization(s): Material customer(s): Drupal India Association
pradhumanjain2311 organization(s): OpenSense Labs customer(s): DrupalFit
penyaskito organization(s): Lullabot
smustgrave organization(s): Mobomo
edmoreta
willeaton
dww organization(s): 3281d Consulting
gbotis
fernly customer(s): District09
samuel.mortenson organization(s): Acquia
manuel garcia volunteering organization(s): Appnovation customer(s): Pfizer, Inc.
pooja saraah organization(s): Material customer(s): Drupal India Association
hass
jeroent organization(s): iO
waropd
quietone organization(s): PreviousNext
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.