Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
rolfmeijer organization(s): Dutch Open Projects
mpdonadio organization(s): DiD Agency
jhedstrom organization(s): Phase2 customer(s): Workday, Inc.
aaronbauman organization(s): Message Agency
bkosborne organization(s): Princeton University
dww volunteering
bwoods volunteering
pancho volunteering
timwood
akalam organization(s): Metadrop
bburg organization(s): Forum One
jedihe volunteering
damienmckenna organization(s): Current
gugalamaciek organization(s): Government of Flanders
sakthi_dev organization(s): Specbee customer(s): Drupal India Association
rp7 customer(s): Government of Flanders
erik.erskine volunteering
jaime@gingerrobot.com organization(s): Ginger Robot
mvonfrie organization(s): trinitec IT Solutions & Consulting GmbH
anybody volunteering organization(s): DROWL.de
jelle_s organization(s): District09
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.