Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
jhedstrom organization(s): Phase2 customer(s): Workday, Inc.
timmillwood organization(s): Appnovation customer(s): Pfizer, Inc.
sam152 volunteering organization(s): PreviousNext
jofitz organization(s): ComputerMinds
vijaycs85 volunteering organization(s): Solathat, TATA Consultancy Services customer(s): Pfizer, Inc.
dawehner volunteering organization(s): Chapter Three (acquired by Kanopi Studios)
oakulm volunteering organization(s): Drontti Oy
Georgii volunteering
tstoeckler organization(s): bio.logis Genetic Information Management GmbH
alison volunteering
ressa organization(s): Ardea
tmwagner organization(s): Tableau
anybody organization(s): DROWL.de
manuel garcia volunteering organization(s): Appnovation customer(s): Pfizer, Inc.
wim leers organization(s): Acquia
Madhura BK organization(s): UniMity Solutions Pvt Limited customer(s): Drupal India Association
iyyappan.govind volunteering organization(s): UniMity Solutions Pvt Limited
kevin.dutra organization(s): Workday, Inc.
steven spasbo organization(s): Workday, Inc.
mahde
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.