Contribution records
Draft
Contributors

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

Give credit to everyone
kpaxman KevinPaxman
igorbiki igorbiki
smustgrave smustgrave organization(s): Mobomo
rar9 Rar9
digitaltodd digitaltodd volunteering
ericdsd ericdsd
gauravvvv Gauravmahlawat organization(s): Axelerant, Material customer(s): Drupal India Association
efes eFeS
zunzun zunzun
quietone quietone organization(s): PreviousNext
cilefen cilefen
timovos timovos organization(s): Alserda Media
nelo_drup Nelo_Drup
omsingh89 omsingh89
crutch crutch
wim leers wimleers organization(s): Acquia
sudesh.solaskar sudesh.solaskar volunteering
Justin Langley JayMLang volunteering
andrea.cividini andrea.cividini organization(s): FRUITION
g-brodiei g-brodiei volunteering
rutiolma rutiolma
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.