Contribution records
Contributors

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

Give credit to everyone
grimreaper florenttorregrosa volunteering organization(s): Smile
OlgaRabodzei OlgaRabodzei organization(s): Adyax
vacho vacho organization(s): Skilld
andypost andypost volunteering organization(s): Skilld
colan colan organization(s): Consensus Enterprises customer(s): Health Canada - HPFB
brolad Brolad organization(s): Drupal Ukraine Community, Skilld
mparker17 mparker17 organization(s): Consensus Enterprises customer(s): Health Canada - HPFB
super_romeo super_romeo
dpacassi dpacassi organization(s): Epsilon Labs customer(s): coliquio
heddn lucashedding organization(s): MTech, LLC, Tag1 Consulting, Inc. customer(s): Google
baddysonja baddysonja organization(s): 1xINTERNET
ilya.no ilya_no volunteering organization(s): Skilld customer(s): Skilld
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.