Contribution records
Draft
Contributors

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

Give credit to everyone
couturier couturier
kreatil kreatIL
boinkster boinkster
mxh hauptm
ts145nera ts145nera
g76 g76
hgneng hgneng
darktek DarkteK
DrupalNovice DrupalNovice
Leeteq Leeteq
shaisamuel shaisamuel
Andrew211 Andrew211
cirrus3d cirrus3d volunteering
wjhessels wjhessels
luksak luksak organization(s): ATTRIBUTE
odizle odizle volunteering
Richard15 Richard15
yaach yaach
jpvivere jpvivere
patrick.thurmond@gmail.com pthurmond
mandus.cz martinpetracek.com
finn lewis ecofinn organization(s): Agile Collective customer(s): Oxfordshire County Council
nick hope NickHope
rjay.dr rjay.dr volunteering
anuradha.zinjade anuradha.zinjade
lakhan thakur lakhan_thakur
qwermans qwermans
nikhil_110 Nikhil_110
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.