Issue
Contribution records
Contributors

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

Give credit to everyone
quicksketch volunteering organization(s): Backdrop CMS, Lullabot customer(s): Backdrop CMS, Tesla Motors
fabianx volunteering organization(s): Tag1 Consulting, Inc. customer(s): The Linux Foundation
bojanz organization(s): Centarro
ngocketit
adamgerthel volunteering
bburscough
maximpodorov
torgospizza
bellagio
KevinVanRansbeeck organization(s): AmeXio Fuse
hanoii
routinet volunteering
awm
dzhibas
David_Rothstein volunteering
mustanggb
joelstein organization(s): On Fire Media
oadaeh organization(s): Hook 42 customer(s): Zicasso, Inc.
firewaller
heddn organization(s): MTech, LLC, Tag1 Consulting, Inc. customer(s): The Linux Foundation
mcdruid volunteering organization(s): Acquia
walkingdexter organization(s): Initlab
vdsh
izmeez
philsward
Neo13
sgdev
skylord
pureh2o
stefan.r
joseph.olstad
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.