Issue
Contribution records
Contributors

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

Give credit to everyone
facine volunteering organization(s): Cambrico
agoradesign
bojanz organization(s): Centarro
anita_novicell
pcambra organization(s): Cambrico
berdir organization(s): MD Systems GmbH
jsacksick organization(s): Centarro
matthiasm11 organization(s): MM-Experience
svendecabooter organization(s): Sven Decabooter
pstewart organization(s): Imperial College Union
dpolant organization(s): Current
luksak organization(s): ATTRIBUTE customer(s): ATTRIBUTE
elex
hansfn
andrewbelcher organization(s): FreelyGive
owilliwo organization(s): Alithya
mgstables
apolitsin
rinasek organization(s): Centarro
vidddd
ralbtre
handkerchief
tijsdeboeck organization(s): Open Up Media
tbkot organization(s): Lemberg Solutions
nicklasmf volunteering
damienmckenna organization(s): Current
n_nelson350
sander wemagine
dries arnolds
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.