Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
jefuri volunteering
lauriii volunteering
rumyanaruseva organization(s): JAKALA (formerly FFW)
slv_
juampynr organization(s): Lullabot customer(s): NBCUniversal
mikhailkrainiuk volunteering organization(s): DrupalJedi
jamiehollern volunteering organization(s): Amazee Labs
vidorado organization(s): Jakala - Biko2
banoodle organization(s): Kanopi Studios
mistergroove volunteering
neclimdul organization(s): APQC
nickdickinsonwilde volunteering organization(s): Taoti Creative
fskreuz organization(s): Portland Webworks
lobsterr organization(s): European Commission and European Union Institutions, Agencies and Bodies
kristyb23
damienmckenna organization(s): Third and Grove
batigolix organization(s): Finalist
abu-zakham organization(s): Vardot
firass.ziedan organization(s): Vardot
suresh prabhu parkala organization(s): Specbee
rinku jacob 13 organization(s): Material customer(s): Drupal India Association
anup.singh volunteering
korn3000
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.