Issue
Contribution records
Contributors

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

Give credit to everyone
mgifford organization(s): OpenConcept Consulting Inc.
dpolant
dawehner volunteering organization(s): Chapter Three (acquired by Kanopi Studios)
damienmckenna organization(s): Current
shrop organization(s): Current
edurenye organization(s): ENDPHASYS Technologies
petermallett organization(s): Current
nikunjkotecha volunteering organization(s): Axelerant
merauluka organization(s): Current
piyuesh23 organization(s): QED42
finne organization(s): Dx Experts
malcolm_p
hkirsman
pdenooijer customer(s): RTL Nieuws
luksak organization(s): ATTRIBUTE
arunthampiklm
avpaderno volunteering
anmolgoyal74 organization(s): OpenSense Labs customer(s): DrupalFit
huzooka organization(s): Cheppers customer(s): Acquia
melvinlouwerse organization(s): Ibuildings customer(s): RTL Nieuws
supreetam09 volunteering organization(s): Acquia
uber_denis
_utsavsharma organization(s): OpenSense Labs customer(s): DrupalFit
michelle organization(s): Current
catch organization(s): Third and Grove
wim leers organization(s): Acquia
olivier.br
mr.york organization(s): Agence Inovae
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.