Issue
Contribution records
Contributors

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

Give credit to everyone
svendecabooter organization(s): Sven Decabooter customer(s): EntityOne
ifrik
alexpott volunteering
siavash
papagrande
larowlan organization(s): PreviousNext
paulocs organization(s): CI&T
psf_ organization(s): Front ID
cpierce42 volunteering
tinto organization(s): The Savvy Few
mrshowerman organization(s): BRANDCODE
dcam volunteering
aopes12 volunteering
smustgrave organization(s): Mobomo
borisson_ organization(s): Calibrate
arisen organization(s): Material
kporras07 organization(s): Pantheon
mark_fullmer volunteering organization(s): University of Texas at Austin
paramnida
andypost volunteering organization(s): Skilld
clemens.tolboom volunteering
nikolay shapovalov volunteering organization(s): RaDon
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.