Contribution records
Draft
Contributors

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

Give credit to everyone
franz franz
joachim joachim
marcingy marcingy
caligan MarieWendel
xjm xjm volunteering organization(s): xjm
aLearner aLearner
schiavone schiavone
iainp999 iainp999
corvus_ch corvus_ch
gaas gisle
berdir berdir
Wtower Wtower
mgifford mgifford organization(s): OpenConcept Consulting Inc.
effulgentsia effulgentsia organization(s): Acquia
catch catch organization(s): Third and Grove
yogeshmpawar yogeshmpawar volunteering organization(s): QED42 customer(s): Drupal India Association
ranjith_kumar_k_u ranjith_kumar_k_u organization(s): Zyxware Technologies
rpayanm rpayanm
rassoni soni.rashu organization(s): Material customer(s): Drupal India Association
ameymudras mudrasamey organization(s): Salsa Digital
vsujeetkumar vsujeetkumar organization(s): Material customer(s): Drupal India Association
damondt damondt
ikam ikam volunteering
albert volkman avolkman
pooja saraah pooja_saraah organization(s): Material customer(s): Drupal India Association
medha kumari kumarimedha09 volunteering organization(s): Dotsquares Ltd.
ravi.shankar ravi.shankar organization(s): OpenSense Labs
ethiaa ethiaa
Git commit message
Commit types

Click on the types below to update the "Commit type" input.

  • 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
  • task: A planned operational or maintenance change to the codebase

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.