Contribution records
Contributors

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

Give credit to everyone
quietone quietone volunteering organization(s): PreviousNext
dww dww volunteering
nod_ nod_ organization(s): Très Bien Tech
cmlara cmlara organization(s): DM13 Security LLC
bbrala bbrala volunteering organization(s): SWIS
bradjones1 bradjones1 organization(s): Not Vanilla, Inc., OPTASY
feyp feyp volunteering organization(s): werk21
acbramley acbramley organization(s): PreviousNext customer(s): Service NSW
poker10 poker10 organization(s): ActivIT s.r.o.
joachim joachim volunteering
fathershawn fathershawn volunteering
bramdriesen bramdriesen volunteering organization(s): Sopra Steria
baluertl BaluErtl volunteering organization(s): Cheppers customer(s): Acquia
marvil07 marvil07 volunteering
larowlan larowlan organization(s): PreviousNext
kim.pepper kimpepper organization(s): PreviousNext
tim.plunkett tim.plunkett organization(s): Acquia
ghost of drupal past GhostOfDrupalPast
xjm xjm organization(s): xjm
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.