Issue
Contribution records
Contributors

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

Give credit to everyone
joachim
socketwench volunteering
brunodbo organization(s): Textillia
schneidolf volunteering
tr
demon326
joelpittet organization(s): The University of British Columbia
dieuwe organization(s): Sparks Interactive
marvil07 organization(s): Isovera customer(s): Pegasystems
pipicom
iancawthorne
fredonia_webteam
jas1988
berenddeboer
mradcliffe organization(s): Kosada
grevil volunteering organization(s): DROWL.de
d_lav volunteering
solideogloria
ivnish
dolcaer volunteering
francoud
Christopher Riley
johan.gant organization(s): Northern Ireland Civil Service - Digital Development
dkmishra
alex.bukach
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.