Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
aspilicious
Crell
jhodgdon
ZenDoodles
sun
yesct
catch volunteering organization(s): Third and Grove
mpdonadio organization(s): DiD Agency
dawehner volunteering
gogowitsch volunteering organization(s): QuoData GmbH Quality & Statistics
cburschka
jonathan1055 volunteering
darvanen
joachim volunteering organization(s): Factorial.io
klausi organization(s): jobiqo - job board technology
jweowu organization(s): Catalyst IT
andypost volunteering organization(s): Skilld
quietone organization(s): PreviousNext
smustgrave organization(s): Mobomo
acbramley organization(s): PreviousNext
dww volunteering
mstrelan
kingdutch organization(s): Open Social
plach organization(s): Tag1 Consulting, Inc.
mpotter organization(s): Phase2
minoroffense organization(s): Coldfront Labs Inc.
donquixote
longwave organization(s): Full Fat Things customer(s): Acquia
damienmckenna organization(s): Third and Grove
krystalcode
solideogloria
lars toomre
claudiu.cristea
kim.pepper organization(s): PreviousNext
johnalbin volunteering
Git commit message
Commit types

Click on the types below to update the "Commit type" input.

  • 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
  • task: A planned operational or maintenance change to the codebase

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.