Contribution records
Contributors

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

Give credit to everyone
ADLongwell ADLongwell
drumm drumm
effulgentsia effulgentsia
sun sun
zubikit zubikit
roblav roblav
mrfelton mrfelton
bartezz bartezz
lyricnz lyricnz
GoddamnNoise GoddamnNoise
guschilds guschilds
kjholla kjholla
jhedstrom jhedstrom
ajits ajits
xano Xano
prexa preksha
hgoto gh640 volunteering organization(s): Studio Umi
quotesbro dberror
wturrell wturrell volunteering
cilefen cilefen
xjm xjm organization(s): Acquia
pameeela pameeela
killes@www.drop.org killes
liam morland lkmorlan
nitesh sethia nitesh11
tim.plunkett tim.plunkett organization(s): Acquia
luke.leber lleber 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.