Issue
Contribution records
Contributors

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

Give credit to everyone
akshaydalvi212 organization(s): QED42 customer(s): Drupal India Association
dww volunteering organization(s): TEN7
damiaosj organization(s): CI&T
elber organization(s): CI&T
kunalgautam volunteering organization(s): Material customer(s): Drupal India Association
urvashi_vora organization(s): Valuebound customer(s): Valuebound
mahima_mathur23 organization(s): Material customer(s): Drupal India Association
roberttabigue organization(s): Promet Source
avpaderno
lucienchalom organization(s): CI&T
sakthi_dev organization(s): Specbee customer(s): Drupal India Association
nitin_lama organization(s): Specbee
yashaswi18
trackleft2 volunteering organization(s): The University of Arizona
elc volunteering
rakhi soni organization(s): Smashing Infolabs Pvt. Ltd. customer(s): Smashing Infolabs Pvt. Ltd.
Tauany Bueno organization(s): CI&T
Joel Guerreiro Borghi Filho organization(s): CI&T
Shreyas gowda
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.