Contribution records
Contributors

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

Give credit to everyone
elc elc volunteering
rreiss rreiss organization(s): Dofinity
torgospizza torgospizza volunteering
squall3d ryantan volunteering
gdanger gdanger
albany albany
nicksanta nickurbits
ndiSIGN ndiSIGN volunteering
gaydamaka gaydamaka volunteering organization(s): JAKALA (formerly FFW)
AnisAlgeria AnisAlgeria
rsbecker rsbecker
chalk Chalk organization(s): DrupalSquad
AntiNSA AntiNSA
armyofda12mnkeys armyofda12mnkeys volunteering
ericjenkins ericjenkins organization(s): Exel Digital
scottatdrake scottatdrake
andyg5000 andyg5000 organization(s): Blue Oak Interactive
ac ac
mglaman mglaman organization(s): Centarro
newaytech newaytech
istavros istavros organization(s): Netstudio
rbogdan rbogdan
LIQUID VISUAL LIQUID_VISUAL volunteering
ibedoya xatiya
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.