Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
bloomt
johnwebdev
Lloyd_87
andrewbelcher organization(s): FreelyGive
rhiss
rjh427
tresero volunteering
dyannenova organization(s): Acquia, Red Hat
ccasals organization(s): Phase2
yogeshmpawar volunteering organization(s): QED42
bnjmnm organization(s): Acquia
dqd volunteering organization(s): MAROQQO studios
josephdpurcell organization(s): Bounteous
xjm volunteering organization(s): xjm
anmolgoyal74 organization(s): OpenSense Labs customer(s): DrupalFit
capysara organization(s): Bounteous
jrbd volunteering
danflanagan8 organization(s): Horizontal
ranjith_kumar_k_u organization(s): Zyxware Technologies
andregp organization(s): CI&T
gaurav_drupal organization(s): Axelerant
gquisini organization(s): CI&T
aaronmchale
benjifisher volunteering organization(s): FRUITION
ressa organization(s): Ardea
hswong3i organization(s): PantaRei Design Limited (Hong Kong)
murrow volunteering organization(s): Macron
mihi-r
tim.plunkett organization(s): Acquia
goncalo.dumas
abhinand gokhala k volunteering organization(s): Zyxware Technologies
Deshna Chauhan
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.