Issue
Contribution records
Contributors

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

Give credit to everyone
yoroy
jenlampton
rootwork
justinchev
lewisnyman
nod_ volunteering organization(s): Smile
sokru organization(s): Druid
bendev organization(s): WebstanZ
espurnes volunteering
jaspreetsingh31 organization(s): Axelerant
droplet
joelpittet organization(s): The University of British Columbia
mbroere organization(s): ronder customer(s): gemeente Leidschendam-Voorburg
kwoxer
sutharsan organization(s): ronder
joum volunteering
tonifisler organization(s): Antistatique
larowlan organization(s): PreviousNext
vacho organization(s): Skilld
aleevas organization(s): Skilld
tvb
mrinalini9 organization(s): Material customer(s): Drupal India Association
vsujeetkumar organization(s): Material customer(s): Drupal India Association
bnjmnm organization(s): Acquia
lauriii organization(s): Acquia
paulocs organization(s): CI&T
ayushmishra206 organization(s): OpenSense Labs
nicolas@webstanz.be
emma.maria organization(s): Deeson
d.fisher organization(s): Pivale
priyanka.sahni 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.