Contribution records
Contributors

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

Give credit to everyone
dan2k3k4 dan2k3k4 organization(s): Amazee Labs
alexj12 Alexj12 organization(s): Zoocha
anushrikumari anushri19 organization(s): OpenSense Labs customer(s): Drupal Association
artusamak Artusamak
hansa11 hansa11 organization(s): Ramsalt Lab
jennydumitrescu jennydumitrescu organization(s): University of Cambridge
jjchinquist jjchinquist organization(s): Drupal Austria
kpolte kpolte
opdavies opdavies organization(s): Oliver Davies Ltd
pattyneta pattyneta
rachel_norfolk rachel_norfolk volunteering organization(s): Cambridge University Press & Assessment
vladimiraus VladimirAus organization(s): Tomato Elephant Studio
volkswagenchick volkswagenchick organization(s): Florida DrupalCamp
antonellasevero antonellasevero
lenny moskalyk lenny_moskalyk volunteering
zoocha will ZoochaWill organization(s): Zoocha
-nrzr- NunoRamos organization(s): NTT DATA
annam.ravin@gmail.com annam.ravin-at-gmail.com
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.