Issue
Contribution records
Contributors

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

Give credit to everyone
ifrik
isntall organization(s): Drupal Association
Bojhan
yoroy organization(s): Mearra (formerly known as Wunder)
sam152
jhodgdon
xjm
no_angel volunteering
chipway organization(s): Chipway
mradcliffe organization(s): Kosada
lomasr organization(s): gai Technologies Pvt Ltd customer(s): gai Technologies Pvt Ltd
tkoleary organization(s): Acquia
jpoesen organization(s): Code Enigma
dawehner organization(s): Chapter Three (acquired by Kanopi Studios)
webchick organization(s): Acquia
benjifisher organization(s): Isovera
wengerk organization(s): Antistatique
wla_g volunteering
alexpott
volkswagenchick organization(s): Kanopi Studios
baluertl volunteering organization(s): Brainsum
vacho organization(s): Skilld
shimpy volunteering organization(s): UniMity Solutions Pvt Limited customer(s): Drupal India Association
cheng75 volunteering organization(s): Google Code-In
sahil06
manjit.singh organization(s): Material
gábor hojtsy organization(s): Acquia
ruslan piskarov volunteering organization(s): KWALL
govind.maloo organization(s): Salsa Digital
ravi.shankar organization(s): OpenSense Labs
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.