Contribution records
Contributors

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

Give credit to everyone
perarnet perarnet
bojanz bojanz
colin_young colin_young
sagannotcarl sagannotcarl
xjm xjm
stpaultim stpaultim
kbasarab kbasarab
scottrigby scottrigby
caligan MarieWendel
stefank stefank
darrellduane DarrellDuane
strykaizer StryKaizer
alberto56 alberto56
vbouchet vbouchet volunteering organization(s): Acquia
SGhosh SGhosh
David_Rothstein drothstein volunteering
fabianx Fabianx volunteering
felribeiro felribeiro organization(s): CI&T
mcdruid mcdruid volunteering organization(s): Acquia
mustanggb akamustang
poker10 poker10 organization(s): ActivIT s.r.o.
ppatterson-edc ppatterson-edc
tim.plunkett tim.plunkett
ryan.ryan ryanissamson
gaurav.goyal gauravgoyal organization(s): Innoraft
sophie.sk Sophie.SK organization(s): Investis Digital
stefan.r stefan.r
joseph.olstad joseph.olstad
stefanos.petrakis stefanos.petrakis volunteering
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.