Contribution records
Contributors

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

Give credit to everyone
lord_of_freaks lord_of_freaks
malcomio malcomio
tsphethean tsphethean
Jaesin jaesin
catch catch
vijaycs85 vijaycs85 organization(s): Capgemini, Solathat, TATA Consultancy Services customer(s): Pfizer, Inc.
joelpittet joelpittet
duaelfr DuaelFr volunteering organization(s): Happyculture
mustanggb akamustang
kevster kevster
technotim2010 TechnoTim2010
johnv johnv
hockey2112 hockey2112
RunePhilosof RunePhilosof
didebru Insasse
izus izus
rpsu rpsu
ytsurk ytsurk
arsn arsn
dineshw dineshweb3 volunteering organization(s): TATA Consultancy Services customer(s): Pfizer, Inc.
klonos klonos organization(s): Backdrop CMS
mcdruid mcdruid organization(s): Acquia
frank.dev Frank.dev
ey pc-wurm
marie.pinet marie.pinet organization(s): Smile
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.