Issue
Contribution records
Contributors

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

Give credit to everyone
smustgrave organization(s): Mobomo
nod_ organization(s): Très Bien Tech customer(s): OpenSense Labs, OPTASY, Palantir.net, Vardot
joelpittet organization(s): The University of British Columbia
cilefen volunteering
longwave organization(s): Full Fat Things
catch volunteering organization(s): Third and Grove
stefan lehmann
dpi organization(s): PreviousNext
ghost of drupal past
amateescu customer(s): Tag1 Consulting, Inc.
joachim
charles belov organization(s): San Francisco Municipal Transportation Agency
borisson_ organization(s): Calibrate customer(s): Acerta
znerol
nicxvan organization(s): nLightened Development LLC
quietone organization(s): PreviousNext
anybody organization(s): DROWL.de
andypost
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.