Contribution records
Draft
Contributors

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

Give credit to everyone
quicksketch quicksketch volunteering organization(s): Lullabot customer(s): Backdrop CMS, Tesla Motors
ckaotik ckaotik organization(s): werk21
hugronaphor hugronaphor volunteering organization(s): Acrosto customer(s): Great Ormond Street Hospital Children's Charity
wells wells volunteering
khiminrm khiminrm organization(s): Lemberg Solutions
drupix drupix
izus izus
oknate oknate volunteering
antonnavi Antonnavi organization(s): Skilld
cilefen cilefen
lamp5 lamp5 organization(s): abventor
makazimtingwa MakaziMtingwa
introfini introfini
fabiansierra5191 fsierra volunteering organization(s): Mobomo
jeroent JeroenT organization(s): iO
jonas139 jonas139 organization(s): iO
mxr576 mxr576 organization(s): Pronovix
ayushmishra206 ayushmishra206 organization(s): OpenSense Labs
spokje Spokje
sharique sharique volunteering organization(s): Acquia
grimreaper florenttorregrosa organization(s): Smile
lubwn lubwn
ammaletu Ammaletu organization(s): Zebralog
sukr_s sudhir volunteering
codex42 Codex42
geek-merlin geek-merlin organization(s): Geeks4Change, MachbarMacher
johnpitcairn johnpitcairn
rob230 Rob230
Git commit message
Commit types

Click on the types below to update the "Commit type" input.

  • 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
  • task: A planned operational or maintenance change to the codebase

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.