Issue
Contribution records
Contributors

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

Give credit to everyone
pcambra
rottencheese
ananto
rszrama
sopratricx
rfay
aristeides
angelbreath
googletorp
jkopel
helios1877
JohnDoranNY
glennpratt
vasi1186
silkogelman
nagiek
adamgerthel
jcodina
sonar_un
charlessmith
greysun
davident
Balbo
brunorios1
simonsparks
mmncs
murz
summit
skyredwang
develcuy
rsvelko
shaneonabike
gorka
damienmckenna
Bik
SkyBuzz
hkovacs volunteering
redeight organization(s): 95Visual
shobhit_juyal
nayanalok volunteering
sano volunteering
toby.batch
damien tournoud
Russell Mann
mr.baileys
decibel.places
pontus_nilsson
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.