Issue
Contribution records
Contributors

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

Give credit to everyone
volkswagenchick organization(s): The Linux Foundation
jjchinquist organization(s): Drupal Austria
antonellasevero
anushrikumari organization(s): OpenSense Labs customer(s): Drupal Association
artusamak
bletch
hansa11 organization(s): Ramsalt Lab
jannekalliola organization(s): Exove
jennydumitrescu organization(s): University of Cambridge
kpolte
mohit_aghera organization(s): PreviousNext
mrsimonelliott
opdavies organization(s): Oliver Davies Ltd
pattyneta
rachel_norfolk organization(s): Cambridge University Press & Assessment
ricardoamaro volunteering
vulcanr volunteering organization(s): Annertech
dan2k3k4 organization(s): Amazee Labs
-nrzr- organization(s): NTT DATA
issa.haddadin volunteering
zoocha will organization(s): Zoocha
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.