Issue
Contribution records
Forks management
Issue edit
Contributors

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

Give credit to everyone
liampower organization(s): Reading Room
baddysonja organization(s): 1xINTERNET
drupalviking volunteering organization(s): Um ad gera ehf.
ifrik volunteering
markie organization(s): Lullabot
mccrodp
spleshka organization(s): SystemSeed customer(s): SystemSeed
yautja_cetanu
markconroy organization(s): Big Blue Door, The Confident customer(s): LocalGov Drupal
philipnorton42 organization(s): #! code (Hash Bang Code), Code Enigma
the_g_bomb organization(s): Zoocha
david bishop
emma horrell organization(s): The University of Edinburgh
finn lewis organization(s): Open Code customer(s): LocalGov Drupal
maria.y organization(s): Agile Collective customer(s): LocalGov Drupal
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.