Issue
Contribution records
Contributors

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

Give credit to everyone
fabianx volunteering organization(s): Tag1 Consulting, Inc. customer(s): Renesas Electronics Corporation
andypost volunteering organization(s): Skilld
alexpott
larowlan organization(s): PreviousNext
johnwebdev
nevergone
anmolgoyal74 organization(s): OpenSense Labs customer(s): DrupalFit
joachim organization(s): Factorial.io
longwave organization(s): Full Fat Things
ankithashetty volunteering organization(s): Specbee
tobiasb organization(s): Gesellschaft zur Entwicklung von Dingen
super_romeo volunteering
luksak organization(s): ATTRIBUTE customer(s): ATTRIBUTE
yogeshmpawar volunteering organization(s): Portage CyberTech
slashrsm organization(s): Tag1 Consulting, Inc. customer(s): Renesas Electronics Corporation
catch organization(s): Third and Grove
xjm organization(s): Acquia
wim leers organization(s): Acquia
tom verhaeghe
moshe weitzman organization(s): Acquia
chr.fritsch organization(s): Thunder
geek-merlin organization(s): Geeks4Change, MachbarMacher
krzysztof domański organization(s): abventor, Dentsu Creative
dhirendra.mishra organization(s): Valuebound customer(s): Valuebound
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.