Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
dpi volunteering
jibran volunteering organization(s): PreviousNext customer(s): University of Technology, Sydney
catch organization(s): Third and Grove
xjm volunteering organization(s): xjm
dinesh18 volunteering
jofitz organization(s): ComputerMinds
adamps organization(s): AlbanyWeb
idebr organization(s): iO
jacobsanford volunteering
zahord volunteering organization(s): Skilld
dimilias organization(s): Randstad Digital customer(s): European Commission and European Union Institutions, Agencies and Bodies
trubach
warped volunteering
emberhood organization(s): Web Bunch
ranjith_kumar_k_u organization(s): Zyxware Technologies
smustgrave organization(s): Mobomo
prudloff organization(s): Insite
kevin.dutra organization(s): Workday, Inc.
moshe weitzman
claudiu.cristea volunteering organization(s): Webikon customer(s): European Commission and European Union Institutions, Agencies and Bodies
s.messaris organization(s): Web Bunch
marios anagnostopoulos volunteering
suresh prabhu parkala organization(s): Specbee
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.