Issue
Contribution records
Contributors

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

Give credit to everyone
msonnabaum
cilefen
dsouza_rohan organization(s): Intelliswift
catch organization(s): Third and Grove
dawehner volunteering organization(s): Chapter Three (acquired by Kanopi Studios)
berdir
anavarre organization(s): Acquia
xjm organization(s): Acquia
bradjones1 volunteering
bkosborne organization(s): Princeton University
webflo organization(s): UEBERBIT GmbH
MKorostoff
deviantintegral organization(s): Lullabot
pwolanin volunteering organization(s): SciShield
Crell organization(s): Upsun (formerly Platform.sh)
jofitz organization(s): ComputerMinds
alberto56 organization(s): Dcycle
joelpittet organization(s): The University of British Columbia
Skarlso organization(s): Cheppers customer(s): Acquia
webchick organization(s): Acquia
yogeshmpawar organization(s): QED42
alexpott volunteering organization(s): Acro Commerce, Thunder
effulgentsia organization(s): Acquia
lauriii organization(s): Acquia
fabianx volunteering
joelstein organization(s): On Fire Media
wim leers organization(s): Acquia
chr.fritsch
star-szr organization(s): Northern Commerce
moshe weitzman
greg.1.anderson organization(s): Pantheon
elijah lynn
geek-merlin organization(s): Geeks4Change, MachbarMacher
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.