Contribution records
Contributors

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

Give credit to everyone
el7cosmos el7cosmos organization(s): Dofinity
comniemeer comniemeer
mherchel mherchel
apolitsin apolitsin
cobenash cobenash volunteering
adrianm6254 Adrianm6254 organization(s): net2Community, Inc.
dydave DYdave organization(s): Code Enigma
megachriz megachriz volunteering
zarpele GuidoRobertone organization(s): Ocelot
ultimike ultimike organization(s): DrupalEasy
jimsmith JimSmith volunteering
dystopianblue dystopianblue
papagrande PapaGrande organization(s): VTP Ventures
guypaddock guypaddock organization(s): Inveniem
mustanggb akamustang
kevinquillen kevinquillen organization(s): Velir
tdnshah tdnshah volunteering organization(s): Acquia
grevil Grevil volunteering organization(s): DROWL.de
navneet0693 navneet0693 volunteering
markdorison markdorison organization(s): Chromatic
carma03 carma03 volunteering
thms-rmb thms-rmb
gaurav-mathur gaurav-mathur organization(s): Dotsquares Ltd.
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.