Issue
Contribution records
Contributors

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

Give credit to everyone
suzymasri organization(s): Pfizer, Inc.
jeroent organization(s): iO
greggles organization(s): Colorado Governor's Office of Information Technology - Colorado Digital Service
vijaycs85 volunteering organization(s): Solathat, TATA Consultancy Services customer(s): Pfizer, Inc.
Rkumar volunteering organization(s): Material customer(s): Drupal India Association
rlhawk
kedxu
jcnventura organization(s): 1xINTERNET
machete1
nicrodgers organization(s): Welsh Government
philippjor
dercheffe
bcdev
candelas volunteering
jastraat organization(s): Technivant
halth organization(s): Taoti Creative
mighty_webber organization(s): Kenneth Copeland Ministries (KCM)
imclean organization(s): Digital Ink
2dareis2do
the_g_bomb organization(s): CACI Digital Experience (formerly Cyber-Duck)
jrockowitz volunteering organization(s): The Big Blue House, Webform module Open Collective
marvil07 organization(s): Adapt
munish.kumar volunteering organization(s): Material customer(s): Drupal India Association
Pooja Ganjage organization(s): Asentech LLC
ben.hamelin organization(s): Oomph, Inc.
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.