Issue
Contribution records
Contributors

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

Give credit to everyone
theodorosploumis
jcfiala volunteering
johnpicozzi organization(s): Oomph, Inc.
da_cloud organization(s): INDICIA
mfernea organization(s): AmeXio Fuse
recrit
kmajzlik organization(s): VMWeb s.r.o.
thatguy
eelkeblok volunteering organization(s): One Shoe
skipyT volunteering
weseze
harsha012 volunteering organization(s): Red Crackle
goz organization(s): Centarro
lamp5
hgoto volunteering organization(s): Studio Umi
kingandy
rcodina
idebr
nironan
dqd volunteering
pifagor organization(s): GOLEMS GABB customer(s): GOLEMS GABB
alex_optim organization(s): GOLEMS GABB customer(s): GOLEMS GABB
pieterdc organization(s): Dropsolid
silverham organization(s): EY Digital
das-peter organization(s): Cando
zsuffa dávid
alex.bukach
james.williams organization(s): ComputerMinds
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.