Issue
Contribution records
Contributors

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

Give credit to everyone
lauriii volunteering organization(s): Druid
brayfe volunteering
ricksta
kris77
bserem organization(s): zehnplus
webcultist
archnode organization(s): Signal
bryanmws
florianmuellerch volunteering
niknak
freelock organization(s): Freelock
stevieb
anybody
afi13
chop organization(s): Deloitte Digital
oriol_e9g organization(s): Diputació de Barcelona
fernly organization(s): District09
damienmckenna organization(s): Current
askibinski volunteering organization(s): ezCompany
jwilson3 organization(s): Bluespark
steveoriol
jhedstrom organization(s): Phase2 customer(s): Workday, Inc.
duaelfr volunteering organization(s): Happyculture
joelpittet organization(s): The University of British Columbia
buzzbee
miro_dietiker organization(s): MD Systems GmbH
damondt
weseze volunteering
ocastle organization(s): Full Bundle
komejo organization(s): ThinkShout
_dcre_
nils.destoop volunteering organization(s): Mearra (formerly known as Wunder)
alan d.
cameron prince
no sssweat
marco.falconi
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.