Issue
Contribution records
Contributors

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

Give credit to everyone
aspilicious
AFowle volunteering
mdupont
Ankabout
giorgio79
hswong3i
nothinghere
agileware
ricardoamaro
scor
christefano
yannickoo
Vayira
alexpott organization(s): Chapter Three (acquired by Kanopi Studios)
francewhoa volunteering
xjm organization(s): Acquia
xaa
David_Rothstein volunteering
damien_vancouver volunteering
ciss organization(s): yousign GmbH
jonhattan
masipila
amateescu customer(s): Pfizer, Inc.
catch
effulgentsia organization(s): Acquia
tuandungb
cilefen
morenstrat
sarathkm
naught101
Turamarth volunteering
geek-merlin organization(s): BinDrin, Clever Systems, DruConsult, MachbarMacher
steve hanson organization(s): Cruiskeen Consulting LLC
yngens
quietone
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.