Issue
Contribution records
Contributors

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

Give credit to everyone
ralphmoser volunteering
David_Rothstein volunteering
mitchalbert
testii28
calebtr
awochna
slipperysky
criscom volunteering
amaisano
santhoshabraham
dalanz
nicrodgers organization(s): Welsh Government
damienmckenna organization(s): Current
therobyouknow
webservant316
cjallenD1
galactus86
beezer75 volunteering
dherbold
jdflorez
srutland volunteering
izmeez
smbenoit
nicxvan volunteering
squarecandy
dcamburn
gaurav_manerkar
bukhnerav
jweowu
torgospizza
glassfrog
dsoini
priyapr
labboy0276
lu_smithcon
erier
drupalevangelist volunteering
knalstaaf
scrypter
hmartens
danica101
sic
crutch
roychan volunteering
gaurishankar
melsi
caspervoogt
damien_bates
spokje organization(s): Annertech
stefan.r
lidiia.litovko
liam morland organization(s): University of Waterloo
ludo.r
damien___b
den tweed organization(s): Coworks.be
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.