Contribution records
Contributors

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

Give credit to everyone
quietone quietone organization(s): PreviousNext
_pratik_ k_pratik volunteering organization(s): Specbee customer(s): Drupal India Association
hardikpandya Pandya-Hardik volunteering organization(s): Material customer(s): Drupal India Association
sahilgidwani SahilGidwani organization(s): Axelerant
pminf pminf volunteering
rogerpfaff rogerpfaff organization(s): Reinblau
smustgrave smustgrave organization(s): Mobomo
xjm xjm volunteering organization(s): HeroDevs, Salsa Digital, xjm
ultimike ultimike organization(s): DrupalEasy
chadhester chadhester volunteering
zshrestha zshrestha volunteering
axb alexb7217 volunteering organization(s): Weber County Library
mandclu mandclu volunteering organization(s): Acquia
nishtha.pradhan nishtha.pradhan organization(s): QED42
rishabh vishwakarma rixhabhh organization(s): OpenSense Labs customer(s): DrupalFit
sahil.goyal sahil.goyal volunteering organization(s): Material customer(s): Drupal India Association
Git commit message
Commit types
  • 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

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.