Contribution records
Contributors

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

Give credit to everyone
indigoxela indigoxela
harald_ harald_git
btopro btopro
markisatacomputer markisatacomputer
larowlan larowlan
derjochenmeyer derjochenmeyer
jmix jmix
sutharsan sutharsan
dan_metille dan_metille
sansui Sansui
aze2010 aze2010
attiks attiks
emcniece emcniece
janiskam janiskam
parrapa parrapa
amirtaiar amirtaiar
malberts malberts
pitxels pitxels
118218 118218
kscheirer kscheirer
liquidcms liquidcms
danreb danreb
paravibe drupalrv
marcoka eanima
boobaa boobaa
jorisx jorisx
stefdewa Stefdewa
shashank5563 shashank5563 organization(s): Melity
sun-fire sun-fire
alex.87 ul71m0
dustin bons Dustin
eugene.ilyin ilyin.eugenegmail.com
b n pandey BNPandey
Mr. Red Mr.Red
belfont99 belfont99
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.