Contribution records
Contributors

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

Give credit to everyone
dpi dpi volunteering organization(s): PreviousNext customer(s): Service NSW
acbramley acbramley organization(s): PreviousNext customer(s): Service NSW
hardik_patel_12 Hardik_Patel_12 organization(s): QED42 customer(s): Drupal India Association
djsagar djsagar organization(s): OpenSense Labs
vikashsoni vikashsoni volunteering organization(s): Zyxware Technologies
joshua1234511 joshua1234511 volunteering organization(s): Axelerant, Salsa Digital customer(s): Salsa Digital
quietone quietone organization(s): PreviousNext
duaelfr DuaelFr volunteering organization(s): Happyculture
larowlan larowlan organization(s): PreviousNext
smustgrave smustgrave organization(s): Mobomo
arunkumark arunkumark volunteering organization(s): Material
lauriii lauriii organization(s): Acquia
akshay kashyap Akshaykashyap volunteering organization(s): gai Technologies Pvt Ltd customer(s): gai Technologies Pvt Ltd
kim.pepper kimpepper organization(s): PreviousNext
kristen pol kepol organization(s): Itty Bitty Byte customer(s): Salsa Digital
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.