Contribution records
Contributors

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

Give credit to everyone
jeffwpetersen jeffwpetersen
masipila masipila
quietone quietone volunteering
markabur markabur
catch catch organization(s): Third and Grove
phenaproxima phenaproxima organization(s): Acquia
heddn lucashedding organization(s): Acro Commerce, MTech, LLC
alexpott alexpott organization(s): Chapter Three (acquired by Kanopi Studios)
vasi evolvingweb-vasi organization(s): Evolving Web
xmacinfo xmacinfo organization(s): xMac info
joelpittet joelpittet organization(s): The University of British Columbia
jofitz jofitz organization(s): ComputerMinds
mikeryan mikeryan volunteering organization(s): Virtuoso Performance
maxocub maxocub volunteering customer(s): Acquia
krystalcode krystalcode organization(s): Acro Commerce
xjm xjm organization(s): Acquia
rakesh.gectcr rakeshjames volunteering organization(s): Valuebound
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.