Issue
Contribution records
Contributors

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

Give credit to everyone
dawehner volunteering organization(s): Chapter Three (acquired by Kanopi Studios), Tag1 Consulting, Inc.
Bojhan volunteering
Jaesin organization(s): Chapter Three (acquired by Kanopi Studios)
droplet
effulgentsia organization(s): Acquia
bkosborne
StuartJNCC
nod_ volunteering
pwolanin volunteering organization(s): Acquia
tarekdj volunteering
OnkelTem volunteering
andrewmacpherson volunteering
sf_wind
lokapujya organization(s): Babson College
joewebmaster
joelpittet volunteering
geerlingguy volunteering organization(s): Acquia
iampuma organization(s): 1xINTERNET
ParisLiakos
dpacassi volunteering
dagmar organization(s): Globant
jibran volunteering
jonathanshaw
andypost volunteering organization(s): Skilld
paulwdru
chi
sam152
lauriii volunteering organization(s): Druid
tameeshb organization(s): Google Summer of Code
yoroy organization(s): Roy Scholten
Mixologic organization(s): Drupal Association
xjm organization(s): Acquia
idebr organization(s): ezCompany
plach
sillo volunteering
ndf organization(s): Dx Experts
wim leers organization(s): Acquia
Daniel Schaefer
star-szr organization(s): Northern Commerce
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.