Contribution records
Contributors

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

Give credit to everyone
pcambra pcambra
phenaproxima phenaproxima organization(s): Acquia
svendecabooter svendecabooter volunteering
quietone quietone volunteering
imiksu iMiksu volunteering organization(s): Mearra (formerly known as Wunder)
jofitz jofitz organization(s): ComputerMinds
damienmckenna damienmckenna organization(s): Current
heddn lucashedding organization(s): MTech, LLC
maxocub maxocub volunteering customer(s): Acquia
dipakmdhrm dipakmdhrm volunteering
catch catch organization(s): Third and Grove
xjm xjm organization(s): Acquia
RytoEX RytoEX volunteering
ao2 ao2 volunteering
yogeshmpawar yogeshmpawar organization(s): QED42
alexpott alexpott volunteering organization(s): Acro Commerce, Thunder
masipila masipila volunteering
gábor hojtsy goba organization(s): Acquia
manuel garcia manuelgarcia volunteering organization(s): Appnovation
ada hernandez Adita organization(s): MTech, LLC
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.