Contribution records
Contributors

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

Give credit to everyone
hchonov hchonov organization(s): bio.logis Genetic Information Management GmbH
timmillwood timmillwood organization(s): Appnovation customer(s): Pfizer, Inc.
alexpott alexpott organization(s): Chapter Three (acquired by Kanopi Studios)
catch catch organization(s): Third and Grove
artem_sylchuk id.jk volunteering organization(s): DevBranch
berdir berdir organization(s): MD Systems GmbH
chanchal2002 chanchal2002
dawehner dereine organization(s): Chapter Three (acquired by Kanopi Studios)
AMDandy AMDandy
Bojhan bojhan
dixon_ dixon
yoroy yoroy volunteering organization(s): Roy Scholten
sam152 sam volunteering organization(s): PreviousNext
tacituseu tacituseu
vijaycs85 vijaycs85 volunteering organization(s): Solathat, TATA Consultancy Services customer(s): Pfizer, Inc.
xjm xjm organization(s): Acquia
plach plach customer(s): Acquia
amateescu amateescu customer(s): Pfizer, Inc.
gábor hojtsy goba organization(s): Acquia
gaurav.kapoor gaurav.kapoor organization(s): OpenSense Labs
hass hass
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.