Issue
Contribution records
Contributors

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

Give credit to everyone
fhaeberle
katrienc volunteering
huzooka organization(s): Cheppers customer(s): Acquia
katannshaw organization(s): Lullabot
ckrina organization(s): Lullabot
pminf organization(s): XIMA MEDIA GmbH
cedric_a organization(s): WeBla
shimpy organization(s): UniMity Solutions Pvt Limited
dyannenova organization(s): Acquia
lauriii organization(s): Acquia
meenakshig organization(s): OpenSense Labs customer(s): DrupalFit
mradcliffe organization(s): Kosada
pranav45 organization(s): OSSeed Technologies
KondratievaS organization(s): Skilld
thalles organization(s): CI&T
bnjmnm organization(s): Acquia
kostyashupenko organization(s): Skilld
prabha1997 organization(s): Valuebound customer(s): Valuebound
neelam_wadhwani organization(s): Valuebound customer(s): Valuebound
emma.maria organization(s): TES Global
maithri shetty organization(s): Specbee
vinodhini.e organization(s): UniMity Solutions Pvt Limited
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.