Issue
Contribution records
Contributors

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

Give credit to everyone
yesct
amateescu
mgifford organization(s): OpenConcept Consulting Inc.
kerby70 organization(s): Blink Reaction (now part of FFW)
idebr
eiriksm organization(s): Ny Media AS
duaelfr volunteering organization(s): Happyculture
dawehner volunteering
strykaizer
alexpott organization(s): Chapter Three (acquired by Kanopi Studios)
thorandre volunteering
yoroy volunteering
catch volunteering
swentel volunteering
mohit_aghera volunteering organization(s): Axelerant
joelpittet volunteering
xjm organization(s): Acquia
pfrenssen organization(s): European Commission and European Union Institutions, Agencies and Bodies
jofitz organization(s): ComputerMinds
geertvd organization(s): Geert van Dort
rogierbom organization(s): Synetic
cilefen organization(s): Institute for Advanced Study
andrewmacpherson volunteering organization(s): Annertech
gnuget volunteering organization(s): Agaric
lendude volunteering organization(s): Dx Experts
botanic_spark organization(s): Develomon customer(s): JAKALA (formerly FFW)
peterhebert
john cook organization(s): Creode
leo pitt
star-szr organization(s): Northern Commerce
Sinan Erdem
gábor hojtsy organization(s): Acquia
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.