Contribution records
Contributors

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

Give credit to everyone
pguillard pguillard
jibran jibran volunteering
oxy86 oxy86
oushen agpsoftdev volunteering
cilefen cilefen volunteering
yogeshmpawar yogeshmpawar volunteering organization(s): QED42
alexpott alexpott organization(s): Chapter Three (acquired by Kanopi Studios)
hampercm hampercm volunteering organization(s): Acquia
balagan balagan organization(s): Brainsum
mh35 mh35
skylord skylord
alex73 alex73
oriol_e9g oriole9g organization(s): Diputació de Barcelona
colorfulcoder Emmezali
valthebald valthebald
gaboo gaboo
borisson_ borisson_ volunteering organization(s): Dazzle
larowlan larowlan organization(s): PreviousNext
jofitz jofitz organization(s): ComputerMinds
allella allella volunteering
gaurav.kapoor gaurav.kapoor organization(s): OpenSense Labs
liam morland lkmorlan organization(s): University of Waterloo
Anthony Fok foka volunteering
das.gautam das.gautam27 volunteering
anna.radulovski anna.radulovski
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.