Issue
Contribution records
Contributors

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

Give credit to everyone
strykaizer
miro_dietiker organization(s): MD Systems GmbH
nebel54
vollepeer organization(s): AmeXio Fuse
amoebanath organization(s): ComputerMinds
rgpublic
vaccinemedia organization(s): CTI Digital
screon
loominade
reekris
Alexandre360
mihai_brb
bjlewis2 organization(s): Modules Unraveled
jonathanshaw
iaminawe
grayle volunteering
nchase volunteering
stevetweeddale organization(s): ComputerMinds
RAFA3L
delacosta456
pascalmortier
8bitplateau
coaston
jeroen.b organization(s): .VDMi/
james.williams organization(s): ComputerMinds
martijn houtman
steven jones organization(s): ComputerMinds
georgiana.albu
ludo.r
bluegeek9 volunteering organization(s): Knowledge Learning Labs, Portland Webworks
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.