Issue
Contribution records
Contributors

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

Give credit to everyone
johne volunteering
jaydarnell organization(s): CivicActions customer(s): LINCS
avpaderno volunteering
mferanda volunteering
denisev
mrinalini9 organization(s): Material customer(s): Drupal India Association
nikitagupta organization(s): Material customer(s): Drupal India Association
fjgarlin volunteering
PhilippVerpoort
ankithashetty volunteering organization(s): Specbee customer(s): Drupal India Association
danielspeicher organization(s): LakeDrops
jurgenhaas organization(s): LakeDrops
somersoft
jukka792 volunteering
tobiasb volunteering organization(s): Gesellschaft zur Entwicklung von Dingen customer(s): OpenCulturas e.V.
omd
anybody organization(s): DROWL.de
grevil organization(s): DROWL.de
ron collins organization(s): Affinity Bridge
robert castelo volunteering
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.