Contribution records
Contributors

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

Give credit to everyone
jnicola jnicola volunteering
dawehner dereine volunteering organization(s): Chapter Three (acquired by Kanopi Studios), Tag1 Consulting, Inc. customer(s): Drupal Association
longwave longwave
mashermike mashermike organization(s): Genuine
ultimike ultimike organization(s): DrupalEasy
gnuget gnuget volunteering
el1_1el el
rewted rewted
chrisroane chrisroane
alexpott alexpott organization(s): Chapter Three (acquired by Kanopi Studios)
floydm Floydm organization(s): Affinity Bridge
jhedstrom jhedstrom organization(s): Phase2 customer(s): Workday, Inc.
lokapujya lokapujya
catch catch organization(s): Third and Grove
benjy benjy organization(s): PreviousNext
NewZeal newzeal organization(s): Passing Phase Web Development
wolffereast wolffereast
malcomio malcomio volunteering organization(s): Capgemini
xjm xjm organization(s): Acquia
nebel54 Nebel54 organization(s): OSCE: Organization for Security and Co-operation in Europe
jibran jibran
ezra ezra
joelpittet joelpittet volunteering
philltran philltran organization(s): Symmetri Technology
drupalfan81 drupalfan81
isa.bel isa.bel
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.