Contribution records
Contributors

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

Give credit to everyone
danillonunes danillonunes
sebyoga sebyoga
kscheirer kscheirer
sammuell sammuell
sushantpaste ps_sushant
deg Deg organization(s): GSATi
MaskOta MaskOta
artusamak Artusamak organization(s): Happyculture
ranjith_kumar_k_u ranjith_kumar_k_u organization(s): Zyxware Technologies
mitthukumawat mitthukumawat volunteering organization(s): Zyxware Technologies customer(s): Drupal Association
acbramley acbramley organization(s): PreviousNext customer(s): Service NSW
dpi dpi organization(s): PreviousNext
nitesh pawar NiteshP organization(s): Trigyn Technologies Ltd
sonam.chaturvedi sonam.chaturvedi organization(s): Salsa Digital
kristen pol kepol organization(s): Itty Bitty Byte customer(s): Salsa Digital
pooja saraah pooja_saraah organization(s): Material customer(s): Drupal India Association
robloach robloach
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.