Contribution records
Contributors

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

Give credit to everyone
shaal shaal volunteering organization(s): Phase2
deciphered deciphered volunteering organization(s): Realityloop
salimlakhani sl4drupal volunteering
johnpicozzi johnpicozzi organization(s): EPAM
skippednote skippednote organization(s): Axelerant
liberatr liberatr volunteering organization(s): JAKALA (formerly FFW)
srdtwc srdtwc
brentrobbins brentrobbins organization(s): Aten Design Group
sallyann716 sallyann716
irinaz irinaz
SolomonGifford solomongifford
kpolymorphic Kpolymorphic
ccoughlan ccoughlan
matthews jmsaunders volunteering
jitesh doshi jitesh_doshi
dk-massive dk-massive organization(s): Aten Design Group
harish_rao harish_rao
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.