Issue
Contribution records
Contributors

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

Give credit to everyone
damienmckenna organization(s): Current
danieka
kevinvb
al0a organization(s): Dropsolid
dobrzyns organization(s): PMMI Media Group
minneapolisdan
dawehner volunteering customer(s): TES Global
kunalkursija organization(s): Axelerant
plopesc organization(s): Bluespark, Cocomore AG
bgronek
kaushashah volunteering
igalafate organization(s): La Drupalera by Emergya
piggito volunteering organization(s): Skilld
PascoS
rybchynski organization(s): DevBranch customer(s): Creative Propulsion Labs
fuzzyjared
markandrewsutton
scotthooker
pieterdc organization(s): Dropsolid
grayle volunteering
nikathone organization(s): GiantGoat Web Development Inc.
ryan.ryan organization(s): Current
peter.keppert
amy.h
yohanaraujo07@gmail.com organization(s): CI&T customer(s): Johnson & Johnson
youfei.sun
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.