Issue
Contribution records
Contributors

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

Give credit to everyone
dawehner volunteering organization(s): Tag1 Consulting, Inc.
jamiecuthill
ayalon
paullomax
marcelovani organization(s): Dennis
skruf
mikeytown2
davidgrayston
ParisLiakos
lmakarov
colan organization(s): Colan Schwartz Consulting customer(s): Chapter Three (acquired by Kanopi Studios)
joelpittet
stborchert organization(s): undpaul
slasher13 volunteering organization(s): Wolters Kluwer
crash98
mediabounds
samiullah organization(s): Salsa Digital
alexpott organization(s): Acro Commerce, Thunder
sundhar volunteering
atul4drupal organization(s): Material customer(s): Drupal India Association
jayprakash01 organization(s): Material customer(s): Drupal India Association
karishmaamin organization(s): Specbee
andypost volunteering organization(s): Skilld
megha_kundar organization(s): Material customer(s): Drupal Association
josh waihi
tim.plunkett
joseph.olstad
Mikael Nord volunteering
raman.b organization(s): OpenSense Labs
kristen pol organization(s): Itty Bitty Byte customer(s): Salsa Digital
cslevy
smustgrave organization(s): Mobomo
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.