Issue
Contribution records
Forks management
Labels management
Contributors

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

Give credit to everyone
vensires organization(s): E-Sepia Web Innovation
johnalbin volunteering
alexmoreno organization(s): Pantheon
ifrik
erik.erskine
lussoluca organization(s): SparkFabrik
zorz organization(s): Point Blank
arismag
gxleano volunteering organization(s): Factorial.io
the_g_bomb organization(s): The University of Edinburgh
tonypaulbarker organization(s): Annertech customer(s): LocalGov Drupal
anand.toshniwal93 volunteering organization(s): QED42
ferran_bosch organization(s): 1xINTERNET
csakiistvan organization(s): 1xINTERNET
breidert organization(s): 1xINTERNET
tomimikola organization(s): Mearra
florisg
emma horrell organization(s): The University of Edinburgh
ekes
ullakoho customer(s): Mearra (formerly known as Wunder)
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.