Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
rlhawk
dcam
darol100 volunteering
legovaer volunteering
David_Rothstein volunteering
therealssj
gvso
vsawant
zipymonkey
afem volunteering
alexpott organization(s): Chapter Three (acquired by Kanopi Studios)
pk188 organization(s): OpenSense Labs
vsujeetkumar organization(s): Material customer(s): Drupal India Association
mondrake volunteering
lendude organization(s): iO
rpayanm organization(s): Agileana
smustgrave organization(s): Mobomo
quietone volunteering organization(s): PreviousNext
sourabhjain organization(s): Valuebound customer(s): Valuebound
royalpinto007
acbramley organization(s): PreviousNext customer(s): Service NSW
xjm volunteering organization(s): xjm
claudiu.cristea
r.nabiullin organization(s): Skilld
rithesh bk volunteering organization(s): Valuebound customer(s): Valuebound
dhirendra.mishra organization(s): Valuebound customer(s): Valuebound
narendra.rajwar27 volunteering organization(s): Material customer(s): Drupal India Association
sahil.goyal 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.