Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
acbramley organization(s): PreviousNext customer(s): Transport for NSW
nitebreed organization(s): Synetic
mycw1991
rogierbom organization(s): Synetic
xjm organization(s): Acquia
amateescu customer(s): Pfizer, Inc.
bucefal91 organization(s): Ocelot
phenaproxima organization(s): Acquia
dxvargas organization(s): European Commission and European Union Institutions, Agencies and Bodies customer(s): European Commission and European Union Institutions, Agencies and Bodies
mattdanger
catch organization(s): Third and Grove
vikashsoni volunteering organization(s): Zyxware Technologies
smustgrave organization(s): Mobomo
anybody organization(s): DROWL.de
dww volunteering
quietone organization(s): PreviousNext
manuel garcia volunteering organization(s): Appnovation customer(s): Pfizer, Inc.
Ruchi Joshi organization(s): Material customer(s): Drupal India Association
abhijith s volunteering organization(s): Zyxware Technologies
amneh.shawish organization(s): iHorizons
gábor hojtsy organization(s): Acquia
van.dordafog organization(s): werk21
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.