Issue
Contribution records
Contributors

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

Give credit to everyone
dpi organization(s): PreviousNext
chi
andypost volunteering organization(s): Skilld
mradcliffe organization(s): Kosada
acbramley organization(s): PreviousNext customer(s): Service NSW
aaronmchale volunteering
quietone organization(s): PreviousNext
kopeboy volunteering
bhanu951 volunteering
greg.1.anderson organization(s): Pantheon
moshe weitzman
kim.pepper organization(s): PreviousNext
gábor hojtsy organization(s): Acquia
bircher volunteering organization(s): Nuvole, European Commission and European Union Institutions, Agencies and Bodies
dries
catch organization(s): Tag1 Consulting, Inc.
franksj
rymo
godotislate volunteering
rfay organization(s): DDEV
xmacinfo volunteering organization(s): xMac info
xjm organization(s): Zoocha, xjm, QED42
dww volunteering
longwave organization(s): Full Fat Things
alexpott organization(s): Acro Commerce, Thunder
arrow
georgestopka@gmail.com
larowlan organization(s): PreviousNext
kingdutch volunteering organization(s): Open Social
dieterholvoet organization(s): Minsky
joachim 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.