Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
legolasbo volunteering
vasi organization(s): Evolving Web
effulgentsia organization(s): Acquia
catch organization(s): Third and Grove
jonathanshaw
gnuget volunteering organization(s): Agaric
ekes volunteering
mile23 volunteering
mohit_aghera volunteering organization(s): Axelerant
ifrik
duaelfr volunteering organization(s): Happyculture
idebr organization(s): iO
sheise
harings_rob organization(s): Harings.be customer(s): Nuvole
joelpittet organization(s): The University of British Columbia
jofitz organization(s): ComputerMinds
markconroy volunteering organization(s): Annertech
dsp1
pescetti organization(s): Nuvole
tommychris
iamdroid
alexpott organization(s): Acro Commerce, Thunder
aaronmchale volunteering organization(s): The University of Edinburgh
avpaderno volunteering
tormi
super_romeo
berdir organization(s): MD Systems GmbH
mxr576 organization(s): Pronovix
smustgrave organization(s): Mobomo
_utsavsharma organization(s): OpenSense Labs customer(s): DrupalFit
gaurav.kapoor organization(s): OpenSense Labs
claudiu.cristea volunteering organization(s): Webikon customer(s): European Commission and European Union Institutions, Agencies and Bodies
hass
star-szr organization(s): Consensus Enterprises
xjm volunteering organization(s): xjm
meeni_dhobale volunteering organization(s): QED42
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.