Contribution records
Contributors

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

Give credit to everyone
cilefen cilefen
dawehner dereine volunteering
RandomSeb RandomSeb
almaudoh almaudoh
alexpott alexpott organization(s): Chapter Three (acquired by Kanopi Studios)
populist populist
heykarthikwithu heykarthikwithu volunteering organization(s): Valuebound
xjm xjm organization(s): Acquia
borepstein borepstein volunteering
rpmskret rpmskret volunteering
boozemun boozemun
paluna paluna
lightweight dlane
prlw1 prlw1
Gorf Gorf
shenzhuxi shenzhuxi volunteering
bskydive bskydive
mdesimone mdesimone volunteering
greg.1.anderson greg1anderson organization(s): Pantheon
tim.plunkett tim.plunkett organization(s): Acquia
quietone quietone 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.