Contribution records
Contributors

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

Give credit to everyone
benjy benjy organization(s): PreviousNext
phenaproxima phenaproxima organization(s): Acquia
webchick webchick organization(s): Acquia
mikeryan mikeryan organization(s): Acquia, Virtuoso Performance customer(s): Drupalize.Me
quietone quietone
chx chx organization(s): Migrate Rocks, Smartsheet
willwh willwh organization(s): Drupalize.Me
agoradesign agoradesign
heddn lucashedding organization(s): MTech, LLC
ayalon ayalon organization(s): Liip
catch catch organization(s): Third and Grove
dsnopek dsnopek
ckaotik ckaotik organization(s): werk21
penyaskito penyaskito organization(s): Lingotek
vasi evolvingweb-vasi organization(s): Evolving Web
animaci animaci
alexpott alexpott organization(s): Chapter Three (acquired by Kanopi Studios)
jibran jibran volunteering
neclimdul neclimdul
dawehner dereine volunteering organization(s): Chapter Three (acquired by Kanopi Studios)
generalredneck generalredneck volunteering
dpalmer dpalmer
xjm xjm organization(s): Acquia
berdir berdir organization(s): MD Systems GmbH
mpp mpp organization(s): AmeXio Fuse
J.R. JonasRMuc volunteering
hass hass
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.