Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
rvilar
jsbalsera
marcvangend
berdir
yched
dawehner volunteering organization(s): Chapter Three (acquired by Kanopi Studios)
mparker17
andypost volunteering organization(s): Skilld
effulgentsia
fago
mikey_p
daffie
xjm organization(s): Acquia
netw3rker
megachriz volunteering
vacho organization(s): Skilld
gnuget volunteering organization(s): Agaric
philltran organization(s): Symmetri Technology
shobhit_juyal volunteering organization(s): Material
dww
catch organization(s): Third and Grove
karishmaamin organization(s): Specbee
adityasingh volunteering organization(s): Material customer(s): Drupal India Association
tkiehne organization(s): University of Washington
nivethasubramaniyan volunteering organization(s): Material customer(s): Drupal India Association
wim leers volunteering
savkaviktor16@gmail.com organization(s): Skilld
gábor hojtsy organization(s): Acquia
nitin shrivastava organization(s): OpenSense Labs
akram khan volunteering organization(s): Material customer(s): Drupal India Association
shivam-kumar volunteering organization(s): Material customer(s): Drupal India Association
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.