Issue
Contribution records
Contributors

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

Give credit to everyone
Jaesin organization(s): Chapter Three (acquired by Kanopi Studios)
alexpott organization(s): Chapter Three (acquired by Kanopi Studios)
dawehner volunteering organization(s): Chapter Three (acquired by Kanopi Studios) customer(s): Drupal Association
mondrake volunteering
borisson_ volunteering
devgurus
Lucasljj volunteering
xjm organization(s): Acquia
swentel
mglaman organization(s): Centarro
amateescu customer(s): Pfizer, Inc.
jibran volunteering
nketchum
dinarcon organization(s): Agaric
michaellenahan organization(s): erdfisch
e0ipso volunteering organization(s): Lullabot
mattferderer
tedbow volunteering organization(s): Acquia
joelpittet
tstoeckler
thihathit
jayemel
aperedos
aiphes
funana volunteering
thirstysix volunteering organization(s): GTECH
tim.plunkett organization(s): Acquia
joshi.rohit100
wim leers organization(s): Acquia
claudiu.cristea organization(s): Webikon
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.