Issue
Contribution records
Contributors

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

Give credit to everyone
catch organization(s): Third and Grove
nnewton
carlos8f
yonailo
jeremy
David_Rothstein volunteering
sun
fgm
kentr
pillarsdotnet
DanPir
robloach
crea
xjm
dsobon
karschsp
donquixote volunteering
pounard
fabianx volunteering organization(s): Tag1 Consulting, Inc.
yesct
amateescu
rwohleb
damienmckenna organization(s): Current
torgospizza
joelpittet volunteering organization(s): The University of British Columbia
mustanggb
gdaw volunteering
dsutter volunteering
joel_osc organization(s): OpenPlus
mcdruid volunteering organization(s): Acquia
izmeez
nareshp
damien tournoud
basicmagic.net
lars toomre
Peter Bowey
tim.plunkett
stefan.r
steven jones organization(s): ComputerMinds
joseph.olstad
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.