Issue
Contribution records
Contributors

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

Give credit to everyone
g4mbini organization(s): Alliance of Digital Builders (AODB), Dropteam
pdureau
rajab natshah
sharique
mogtofu33
kerrymick
monet-fort
just_like_good_vibes
dhansen
sea2709
mattlc
grienauer
frodri
rkoller
cezara
bbruno organization(s): 1xINTERNET
shanekba
thamas organization(s): 1xINTERNET
tijsdeboeck
yannickoo organization(s): 1xINTERNET
csakiistvan organization(s): 1xINTERNET
jlbellido
juc1
mr_scumbag
nkarhoff
echechulina
fboulanger
grimreaper volunteering organization(s): Smile
flo909 organization(s): 1xINTERNET
ferran_bosch organization(s): 1xINTERNET
maboy
bacarndiaye
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.