Contribution records
Draft
Contributors

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

Give credit to everyone
catch catch organization(s): Third and Grove
dawehner dereine volunteering organization(s): Chapter Three (acquired by Kanopi Studios)
larowlan larowlan organization(s): PreviousNext
tetranz tetranz organization(s): Third and Grove
twod twod organization(s): Websystem
jeffam jeffam
mirom mirom organization(s): Slovak Drupal Association
dflitner dflitner
kerasai bmoresafety20
jonathanshaw jonathanjfshaw
jonasanne Jonasanne organization(s): Calibrate
smustgrave smustgrave organization(s): Mobomo
dww dww volunteering organization(s): 3281d Consulting customer(s): SMAI
rachel_norfolk rachel_norfolk organization(s): Cambridge University Press & Assessment
sukanya.ramakrishnan sukanya.ramakrishnan organization(s): Workday, Inc.
pritishkumar pritish.kumar organization(s): OpenSense Labs
lunk rat LunkRat
mikell Mikell organization(s): Dropsolid customer(s): District09
fskreuz fskreuz
cslevy cslevy
mortona2k mortona2k
graber Graber organization(s): MoveOnline
kristiaanvandeneynde kristiaanvandeneynde volunteering organization(s): Tag1 Consulting, Inc.
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.