Issue
Contribution records
Forks management
Issue edit
Contributors

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

Give credit to everyone
noah
Syndz organization(s): Nedbase
vollepeer organization(s): AmeXio Fuse
markwittens
aaronbauman organization(s): Message Agency
sutharsan organization(s): ronder
gsquirrel
peterhebert
jnettik organization(s): Aten Design Group
johne organization(s): Aten Design Group
acrosman volunteering organization(s): Cyberwoven
devil2005
lamp5
renrhaf organization(s): Skazy
johnny5th organization(s): Encore Multimedia
dww volunteering
jonmcl
sneakysnk
joelpittet organization(s): The University of British Columbia
pookmish
anybody organization(s): DROWL.de
nrackleff organization(s): ThinkShout
kasey_mk
5n00py volunteering
pieterdc organization(s): Dropsolid
alison volunteering
OlgaS
michaelablackham organization(s): Aten Design Group
scoff
stefdewa organization(s): Calibrate
mattbloomfield volunteering
barinder volunteering
jungle volunteering
3ssom organization(s): Acro Commerce
nkraft organization(s): IQ Solutions
texas_tater organization(s): University of Texas at Austin
andypost volunteering organization(s): Skilld
ryankavalsky
banoodle organization(s): Kanopi Studios
nelslynn
Miri Meltzer volunteering
d.sibaud
Pascal-
jaroslav červený
eyal shalev volunteering organization(s): Dofinity
chris matthews volunteering
steven buteneers
thomas.frobieter volunteering
Bram Linssen volunteering
kristen pol organization(s): Hook 42
stephen ollman
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.