Contribution records
Contributors

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

Give credit to everyone
jibize LondonITGuys
Redart Redart
alumni alumni
tamonten1 tamonten1
OriginalSauce OriginalSauce
idebr idebr
mibfire mibfire
JadH JadH
stborchert stborchert organization(s): undpaul
MPeli MPeli
revagomes revagomes
kungz13 kungz13
j4 j4
scottrigby scottrigby
hauruck hauruck
joelpittet joelpittet
luksak luksak
ckaotik ckaotik
guillaumev guillaumev
pookmish pookmish
Drupa1ish Drupa1ish organization(s): EuroDomenii
asghar asghar
markhalliwell markcarver organization(s): Tag1 Consulting, Inc.
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.