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
cspitzlay organization(s): bio.logis Genetic Information Management GmbH
mgifford organization(s): OpenConcept Consulting Inc.
mohit_aghera volunteering organization(s): Axelerant
amateescu customer(s): Pfizer, Inc.
jainv18 volunteering
mlncn organization(s): Agaric customer(s): Drutopia, Portside, Teachers with GUTS
avinashm volunteering
marcus_johansson organization(s): FreelyGive customer(s): Acquia
tim.plunkett organization(s): Acquia
iyyappan.govind
geek-merlin organization(s): Geeks4Change, MachbarMacher
a.dmitriiev volunteering organization(s): 1xINTERNET
smustgrave organization(s): Mobomo
petar_basic organization(s): drunomics
fago organization(s): drunomics
arianraeesi customer(s): 1xINTERNET
ahmad-khalil-imagex
abhisekmazumdar organization(s): Dropsolid customer(s): Dropsolid
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.