Issue
Contribution records
Contributors

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

Give credit to everyone
nod_ volunteering organization(s): Acquia, Très Bien Tech customer(s): Liip, OPTASY, Palantir.net, Vardot
anavarre organization(s): Acquia
rteijeiro organization(s): Tieto
droplet
cilefen
jeroent organization(s): iO
xjm volunteering organization(s): Acquia, xjm
dawehner volunteering organization(s): Chapter Three (acquired by Kanopi Studios)
nandasoftware volunteering organization(s): Kiluvai Tech Solutions Private Limited
alexpott organization(s): Acro Commerce, Chapter Three (acquired by Kanopi Studios), Thunder
skaught volunteering
catch organization(s): Third and Grove
joelpittet
kostyashupenko organization(s): Skilld
ankithashetty volunteering organization(s): Specbee
quietone organization(s): PreviousNext
smustgrave organization(s): Mobomo
travis-bradbury organization(s): Acro Commerce
manuel garcia volunteering organization(s): Appnovation
lokesh.soni volunteering
star-szr volunteering
hass
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.