Contribution records
Contributors

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

Give credit to everyone
raysunil Raysunil
mikeryan mikeryan organization(s): Acquia
jhodgdon jhodgdon
owntheweb owntheweb volunteering
gaele gaele
ezoulou ezoulou
wisniewski wisniewski
Schroeffu Schroeffu
miguellopez miguellopez volunteering
roald rkleivel
atomicnation atomicnation
zanvidmar zanvidmar
jfeltkamp JFeltkamp
alindebian alindebian volunteering
sylvain_a saube
hiramanpatil hiramanpatil organization(s): Clarion Technologies
sidharthap sidharthap organization(s): TATA Consultancy Services customer(s): Pfizer, Inc.
lias lias
ccrosaz ccrosaz
Christijan Christijan volunteering
soniaojha soniaojha
danrod danrod volunteering
quietone quietone organization(s): PreviousNext
avpaderno avpaderno volunteering
michel.settembrino michel.settembrino organization(s): Colruyt Group Services, MS-Informatique
drupal4u.org drupal4u.org volunteering
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.