Contribution records
Contributors

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

Give credit to everyone
akshaydalvi212 akshaydalvi212 organization(s): QED42 customer(s): Drupal India Association
ameymudras mudrasamey organization(s): Salsa Digital
benjifisher benjifisher volunteering organization(s): FRUITION
guptahemant guptahemant volunteering organization(s): QED42
hestenet hestenet organization(s): Drupal Association
leslieg lglynn2299 organization(s): Redfin Solutions, LLC
libbna Libbna volunteering organization(s): QED42 customer(s): Drupal India Association
shriaas Shriaas organization(s): QED42 customer(s): Drupal India Association
tinto Tinto organization(s): The Savvy Few
vighneshh VighneshSadagopal organization(s): QED42 customer(s): Drupal India Association
vinmayiswamy VinmayiSwamy volunteering organization(s): Material customer(s): Drupal India Association
surabhi-gokte SurabhiGokte volunteering organization(s): Material customer(s): Drupal India Association
kristen pol kepol organization(s): Itty Bitty Byte customer(s): OPTASY, Salsa Digital
fathima.asmat fathima.asmat organization(s): CTI Digital
gábor hojtsy goba organization(s): Acquia
kim.pepper kimpepper organization(s): PreviousNext
omkar-pd omkar-pd organization(s): QED42
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.