Issue
Contribution records
Contributors

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

Give credit to everyone
dunebl
adriancid volunteering
pasqualle volunteering
jonnyeom volunteering
ebeyrent
shawngo
dydave organization(s): CGI, DAVYIN Internet Solutions / 戴文信息科技有限公司
markie volunteering organization(s): Current
lukasss
danepowell organization(s): Acquia
thejacer87 organization(s): Acro Commerce
imclean
romainj volunteering
acrosman volunteering
thalles organization(s): CI&T
cobenash
oknate volunteering
webdrips
kumkum29
duaelfr volunteering organization(s): Happyculture
pcate volunteering
geraldito
superlolo95
andrey_semenoff
renrhaf organization(s): Skazy customer(s): OPT NC
xlith
lyalyuk organization(s): Drupal Ukraine Community customer(s): AnyforSoft
abramm organization(s): DevBranch, Drupal Ukraine Community customer(s): Invotra Ltd
littlecrab
jl_cs
azovsky
grimreaper volunteering
arturopanetta
rooby
joveloper
RubenCasado
leisurman
anawillem
guillaumeg volunteering
jjmackow
cprofessionals
tirler
benjaminbradley
das-peter organization(s): Cando
mιχaliς
s-jack
nick hope
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.