Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
rsvelko
kenorb
ishwar
prince_kr organization(s): Zyxware Technologies
chop organization(s): Deloitte Digital, Technocrat
nancydru
giorgio79
ericclaeren
Fabito
remyyyyy volunteering
majdi volunteering
sgdev
rivimey volunteering organization(s): CPL
lubwn
narkoff
murali97
martinhansen organization(s): PeaceWorks Technology Solutions
memcinto volunteering
glynster
fonant organization(s): Fonant Ltd
heyyo
pancho volunteering
parasolx
themic8
aaldayel
ironsizide organization(s): Message Agency
philsward
cirrus3d
szeidler organization(s): Ramsalt Lab
aubjr_drupal
dpico
anrikun
erwangel
anybody volunteering organization(s): DROWL.de
loopy1492
ethan1el
sano
mskicker
chrisroane
biarr
musa.thomas
joseph.olstad
petar.kolicov
Chris Charlton volunteering
marko b
vincent wasswa
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.