Issue
Contribution records
Contributors

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

Give credit to everyone
klausi
vivekvpandya volunteering
marthinal
berdir
m1r1k organization(s): Propeople (now part of FFW) customer(s): Propeople (now part of FFW)
droti
andypost volunteering organization(s): Skilld
kylebrowning organization(s): Acquia
heykarthikwithu volunteering organization(s): Valuebound
dawehner volunteering organization(s): Chapter Three (acquired by Kanopi Studios)
alexpott organization(s): Chapter Three (acquired by Kanopi Studios)
cloudbull
f0ns
jlbellido organization(s): Cocomore AG
jjcarrion organization(s): Mearra (formerly known as Wunder)
tedbow organization(s): Acquia
xjm organization(s): Acquia
effulgentsia organization(s): Acquia
pwolanin volunteering
ruloweb organization(s): Media.Monks
hubobbb volunteering
lastlink volunteering
lslinnet organization(s): JAKALA (formerly FFW)
boby_ui volunteering
clemens.tolboom volunteering
claudiu.cristea organization(s): Webikon
wim leers organization(s): Acquia
yasin-ali volunteering
Snehal Brahmbhatt organization(s): AddWeb Solution Pvt. Ltd.
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.