Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
bserem organization(s): zehnplus
kmajzlik organization(s): Ciklum Western Europe customer(s): BurdaForward
rhuffstedtler volunteering
Mixologic organization(s): Drupal Association
nickdickinsonwilde volunteering organization(s): BriarMoon Design
SMartin
xamount volunteering
bwoods organization(s): R2integrated
chegor organization(s): OAO Solution Spark
drupaldope
yonailo
Webbeh organization(s): Georgia Institute of Technology
jwilson3 organization(s): Bluespark
paulmckibben organization(s): Turbojet Technologies
kreynen organization(s): University of Colorado
mmjvb volunteering
spuky volunteering
aiphes
damienmckenna organization(s): Current
inversed
firewaller
vincent_fontaine
kduryee
arsn
RGonski
nitesh sethia volunteering organization(s): Syngenta
neslee canil pinto organization(s): Specbee
damien laguerre
Hookset Media
stephen ollman
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.