Contribution records
Contributors

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

Give credit to everyone
webchick webchick organization(s): Acquia
yoroy yoroy
rpayanm rpayanm
jamesdixon jamesdixon
eclipsegc eclipsegc
tkoleary tkoleary
hampercm hampercm volunteering organization(s): Acquia
jturman jturman
andypost andypost
sidharrell sidharrell
edmilsonefs edmilsonefs
pixlkat pixlkat organization(s): CivicActions
yesct YesCT
manauwarsheikh alam28
deepakaryan1988 deepakaryan1988 organization(s): Material
kaypro4 i8flan volunteering
alexpott alexpott organization(s): Chapter Three (acquired by Kanopi Studios)
webankit babbar.ankit
RavindraSingh it.ravindrasingh volunteering organization(s): Material
berdir berdir organization(s): MD Systems GmbH
tedbow tedbow organization(s): Acquia
greg.1.anderson greg1anderson
tim.plunkett tim.plunkett organization(s): Acquia
bill richardson bill richardson volunteering
sorabh.v6 saurabh-vijayvargiya volunteering
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.