Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
hchonov organization(s): bio.logis Genetic Information Management GmbH
yesct
plach volunteering
tstoeckler
penyaskito organization(s): Cocomore AG
gapple organization(s): Myplanet
douggreen organization(s): Tag1 Consulting, Inc.
LemonHardos
hlopes
clayfreeman organization(s): Library Market
nwom
catch organization(s): Third and Grove
berdir organization(s): MD Systems GmbH
idas
jefuri volunteering organization(s): Synetic
DonAtt volunteering
joachim organization(s): Factorial.io
adityasingh volunteering organization(s): Material customer(s): Drupal India Association
tallytarik
heddn organization(s): MTech, LLC, Tag1 Consulting, Inc.
quietone organization(s): PreviousNext
s_leu organization(s): Tag1 Consulting, Inc.
biancaradu27 organization(s): Dream Production
connbi
gábor hojtsy organization(s): Acquia
sukanya.ramakrishnan
raman.b organization(s): OpenSense Labs
james.williams organization(s): ComputerMinds customer(s): Hydrotechnik UK Ltd
kevin.brocatus organization(s): INDICIA
ravi.shankar organization(s): OpenSense Labs
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.