Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
mpdonadio
webflo organization(s): UEBERBIT GmbH
morenstrat
tedbow organization(s): Acquia
arknoll
colan organization(s): Colan Schwartz Consulting customer(s): Chapter Three (acquired by Kanopi Studios)
swentel
jhedstrom volunteering
extexan
marassa
gambry organization(s): manifesto
agudivad
xjm organization(s): Acquia
yoroy
bahuma20 organization(s): Grasenhiller GmbH
yareckon
jonathanshaw
minoroffense organization(s): Coldfront Labs Inc.
dalra
aaronbauman organization(s): Message Agency
dww volunteering
cainaru organization(s): St. Lawrence University customer(s): St. Lawrence University
quietone organization(s): PreviousNext
wim leers organization(s): Acquia
gábor hojtsy organization(s): Acquia
gaëlg organization(s): Insite
anicoto organization(s): Cellar Door
liam morland organization(s): OpenPlus, Scouting Waterloo Region
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.