Issue
Contribution records
Contributors

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

Give credit to everyone
joachim volunteering
gambry organization(s): manifesto
wesleymusgrove
DedMoroz
rackberg volunteering
agoradesign
yogeshmpawar volunteering organization(s): QED42
dinesh18 volunteering
stijndmd
mrkdboyd
larowlan organization(s): PreviousNext
harsha012 volunteering organization(s): Red Crackle
alexej_d
ricovandevin organization(s): Finlet customer(s): One Shoe
Filozofer
acbramley
aaronbauman organization(s): Message Agency
nortmas
akalam organization(s): Metadrop
koryp volunteering
cilefen volunteering
alexpott organization(s): Acro Commerce, Thunder
jibran volunteering organization(s): PreviousNext
kala4ek volunteering organization(s): DrupalJedi
pguillard
unstatu
marcaddeo organization(s): Pare & Co
joelpittet organization(s): The University of British Columbia
gnikolovski organization(s): Studio Present
robertom organization(s): bmeme
mrupsidown
gbirch organization(s): Commonwealth of Massachusetts
rob c
vipul tulse organization(s): Clarion Technologies
sathish.redcrackle organization(s): Red Crackle
stefan.r
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.