Contribution records
Contributors

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

Give credit to everyone
dawehner dereine customer(s): Drupal Association
berdir berdir organization(s): MD Systems GmbH
webchick webchick organization(s): Acquia
vasi evolvingweb-vasi volunteering organization(s): Evolving Web
catch catch
heddn lucashedding organization(s): MTech, LLC
dagmar dagmar volunteering organization(s): Globant
fgm fgm volunteering organization(s): OSInet
ziomizar ziomizar volunteering organization(s): East Atlantic Engineering, Station
jofitz jofitz organization(s): ComputerMinds
nithinkolekar nithinkolekar
didebru Insasse organization(s): UEBERBIT GmbH
smustgrave smustgrave
mfb mfb
littlepixiez littlepixiez
neclimdul neclimdul organization(s): APQC
_utsavsharma utsavsharma6 organization(s): OpenSense Labs customer(s): DrupalFit
quietone quietone organization(s): PreviousNext
xjm xjm volunteering organization(s): HeroDevs, Salsa Digital
longwave longwave organization(s): Full Fat Things
todd zebert ToddZebert organization(s): Miles
hass hass
Git commit message
Commit types
  • 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

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.