Contribution records
Contributors

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

Give credit to everyone
avpaderno avpaderno
alisamar alisamar
pschuelke pschuelke
peterpoe peterpoe
joaogarin joaogarin
pdcarto patdunlavey
aaronschachter aaronschachter
Talkless Talkless
robynlgreen robynlgreen
damonbla damonbla
basant basantsharma organization(s): Innoraft
nabajit Nabajit
deggertsen deggertsen volunteering
leopathu leopathu volunteering
cprofessionals CProfessionals
SchwebDesign SchwebDesign
danquah danquah organization(s): Reload
fabianx Fabianx volunteering organization(s): Tag1 Consulting, Inc.
David_Rothstein drothstein volunteering
joelpittet joelpittet
oriol_e9g oriole9g organization(s): Diputació de Barcelona
xjm xjm organization(s): Acquia
cilefen cilefen volunteering
larowlan larowlan organization(s): PreviousNext
pedrosp pedrosanchezpernia
g.i.joe G.I.Joe volunteering
joseph.olstad joseph.olstad volunteering
Michael-IDA Sam-Inet organization(s): Internet Design Alliance
davidwbarratt davidwbarratt
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.