Contribution records
Contributors

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

Give credit to everyone
ifrik ifrik
hauruck hauruck organization(s): UEBERBIT GmbH
eojthebrave eojthebrave organization(s): Drupalize.Me, Lullabot
heddn lucashedding organization(s): MTech, LLC
michael_wojcik michael_wojcik volunteering organization(s): Current
quietone quietone volunteering
maxocub maxocub volunteering
leslieg lglynn2299 volunteering
lokapujya lokapujya
phenaproxima phenaproxima organization(s): Acquia
mikeryan mikeryan volunteering organization(s): Virtuoso Performance
yoroy yoroy organization(s): Roy Scholten
jofitz jofitz organization(s): ComputerMinds
lauriii lauriii organization(s): Druid
rakesh.gectcr rakeshjames volunteering organization(s): Valuebound
gábor hojtsy goba organization(s): Acquia
himanshu-dixit himanshu-dixit volunteering organization(s): Google Summer of Code
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.