Issue
Contribution records
Contributors

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

Give credit to everyone
poojasharmaece volunteering
visabhishek volunteering organization(s): Azri Solutions
developmenticon
dj1999 organization(s): Brainsum customer(s): Tieto
istryker
cbeier
mediabounds
anastasiaphil organization(s): iO, One Shoe
johnjw59 organization(s): Fuse Interactive
marcvangend volunteering
jmuzz
tracipotocnik volunteering
mariacha1 organization(s): ThinkShout
papagrande volunteering
komlenic
EricRondo
dkosbob
chandeepkhosa organization(s): 2Toucans
bbombachini organization(s): Northern Commerce
mmbk volunteering organization(s): erdfisch
bbu23 organization(s): Ninja Coders
j_s
urvashi_vora organization(s): Valuebound customer(s): Valuebound
nord102 organization(s): Northern Commerce
coaston
programeta volunteering organization(s): NTT DATA
nicxvan
mandclu volunteering organization(s): Acquia
tonka67
jsutta
gangu
nikolai.rocket
alex.skrypnyk organization(s): DrevOps
joseph.olstad
robert-io
m.c.t volunteering
stefan.butura organization(s): Eau de Web
vlad.dancer volunteering organization(s): Drupal Ukraine Community customer(s): Oomph, Inc., Xspace
tim-diels organization(s): Calibrate
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.