Contribution records
Draft
Contributors

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

Give credit to everyone
webchick webchick
fago fago
mustanggb akamustang
adamdicarlo adamdicarlo
thebuckst0p thebuckst0p
jastraat jastraat
zilverdistel zilverdistel
BenK benk
bendiy bendiy
karens karens
salvis salvis
klonos klonos
damienmckenna damienmckenna
anavarre anavarre organization(s): Acquia
duaelfr DuaelFr volunteering organization(s): Happyculture
anybody Anybody organization(s): DROWL.de
trevorkjorlien trevorkjorlien
dave reid davereid
Niklas Fiekas niklas
Tom Dowling Tom Dowling
chris matthews ChrisMatthews
geek-merlin geek-merlin organization(s): MachbarMacher
g4mbini G4MBINI organization(s): Dropteam, Alliance of Digital Builders (AODB)
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.