Issue
Contribution records
Contributors

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

Give credit to everyone
ahebrank
heddn organization(s): MTech, LLC
coufu
kirkkala organization(s): Mearra (formerly known as Wunder)
roberttstephens
bhanu951 volunteering
byrond organization(s): Palantir.net customer(s): Argonne National Laboratory
egruel
berliner
pacproduct organization(s): Makina Corpus
robertom organization(s): bmeme
jamsilver
bbu23 organization(s): Ninja Coders
jigarius volunteering organization(s): Symetris
scott_euser volunteering organization(s): Soapbox
jonasanne organization(s): Calibrate
nnevill organization(s): DevBranch, Drupal Ukraine Community
nicxvan
sonfd organization(s): DevCollaborative, LLC
mikelutz volunteering organization(s): Four Kitchens
macsim organization(s): Axess Open Web Services
jrockowitz volunteering organization(s): The Big Blue House, Webform module Open Collective
ramzypro
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.