Issue
Contribution records
Contributors

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

Give credit to everyone
tommychris
JoelAddison
iryston volunteering
co2ncos1to
markdorison organization(s): Chromatic
choster
jenlampton organization(s): Jeneration Web Development customer(s): ChinaFile
thelmer organization(s): Adapt
annared
rudam
calbasi customer(s): Matarrania
djalxs volunteering
aseabrook volunteering
jjsanbra
uno
jaypan organization(s): Jaypan
ANDiTKO volunteering
joelpittet organization(s): The University of British Columbia
kurkuma volunteering
gambry organization(s): manifesto
llslim
gateway69
roderickgadellaabsl
ressa organization(s): Ardea
T.Mardi
alan d.
Wil B. Samson
nvaken
anthony.bouch volunteering
andrea.cavattoni
andrey.troeglazov organization(s): DrupalJedi
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.