Issue
Contribution records
Contributors

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

Give credit to everyone
scoff
rob_pr
heddn organization(s): MTech, LLC
amjad1233 volunteering
zcht
mrweiner volunteering
radelson organization(s): WebstanZ
hitchshock organization(s): DevBranch
timohuisman organization(s): SWIS
andycarlberg organization(s): Bounteous
grifstuf organization(s): Bounteous
naveenvalecha organization(s): Morpht customer(s): Morpht
jardasmahel organization(s): Morpht customer(s): Morpht
eleonel organization(s): Morpht
gaards volunteering organization(s): Yle - Finnish Broadcasting Company
thisisalistairsaccount
Kfootm70
aurelianzaha organization(s): jobiqo - job board technology
emixaam
amaisano
ccjjmartin volunteering
jayelless
marios anagnostopoulos volunteering
james.williams organization(s): ComputerMinds
manuel.adan organization(s): NTT DATA customer(s): European Commission and European Union Institutions, Agencies and Bodies
kristen pol organization(s): Salsa Digital customer(s): govCMS (Australian Government Department of Finance)
knowak
klausi organization(s): jobiqo - job board technology
mstrelan
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.