Contribution records
Draft
Contributors

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

Give credit to everyone
dropa Dropa organization(s): Mediamaisteri Oy
socialnicheguru SocialNicheGuru
olofbokedal ojohansson organization(s): Odd Hill
yogeshmpawar yogeshmpawar volunteering organization(s): QED42
fabienly fabienly volunteering
darvanen Darvanen
akshay_d akshay_d organization(s): Specbee customer(s): Drupal India Association
mradcliffe mradcliffe organization(s): Kosada
vikashsoni vikashsoni volunteering organization(s): Zyxware Technologies
karishmaamin karishmaamin organization(s): Specbee
guilhermevp guilhermevp organization(s): CI&T
nikhil_110 Nikhil_110 organization(s): Material
smustgrave smustgrave organization(s): Mobomo
rachel_norfolk rachel_norfolk organization(s): Cambridge University Press & Assessment
john cook johncook organization(s): Creode
suresh prabhu parkala SureshPrabhuParkala organization(s): Specbee
bob.hinrichs bob.hinrichs
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.