Contribution records
Contributors

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

Give credit to everyone
griffynh griffynh
larowlan larowlan organization(s): PreviousNext
acbramley acbramley organization(s): PreviousNext
catch catch organization(s): Third and Grove
ctrladel ctrlADel volunteering organization(s): True Summit
danielveza DanielVeza volunteering organization(s): PreviousNext
darvanen Darvanen organization(s): Sitback Solutions
e0ipso e0ipso volunteering organization(s): Lullabot
Jesse Jesse
lauriii lauriii organization(s): Acquia
penyaskito penyaskito organization(s): Lullabot
sime sime organization(s): Free Sauce
vladimiraus VladimirAus organization(s): Tomato Elephant Studio
jessebaker jessebaker organization(s): Acquia
cgreaten cgreaten organization(s): Bounteous
zetagraph zetagraph volunteering
gábor hojtsy goba organization(s): Acquia
kristen pol kepol organization(s): QuantCDN, Salsa Digital
wim leers wimleers organization(s): Acquia
tim.plunkett tim.plunkett organization(s): Acquia
r.aubin raubin organization(s): Oomph, Inc.
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.