Issue
Contribution records
Contributors

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

Give credit to everyone
cilefen volunteering
amateescu customer(s): Pfizer, Inc.
jnimchuk
kruser volunteering
maxilein
nikita_tt volunteering
tepelena
catch organization(s): Third and Grove
alexpott organization(s): Thunder
chris5156
berdir organization(s): MD Systems GmbH
neclimdul organization(s): APQC
tedbow organization(s): Acquia
quietone organization(s): PreviousNext
Pascal-
tajinder.minhas volunteering organization(s): SDG Corporation
rick hood
eric.guerin@ucsf.edu volunteering organization(s): University of California
sam-elayyoub volunteering organization(s): Achieve Internet
wim leers organization(s): Acquia
a.dmitriiev volunteering organization(s): 1xINTERNET
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.