Issue
Contribution records
Forks management
Labels management
Contributors

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

Give credit to everyone
tedbow organization(s): Acquia
geertvd organization(s): Geert van Dort
robshambaugh
kurttrowbridge
bkat
akalata
thursday_bw organization(s): Catalyst IT
awasson
adriancid volunteering
plach customer(s): MD Systems GmbH
purencool
pwetter
karlshea organization(s): Karl Shea
dpi organization(s): PreviousNext
waverate
aklump organization(s): In the Loft Studios
TikaL13
mmaranao
gngn organization(s): Computer Manufaktur GmbH
sagesolutions
bloomt
philltran organization(s): Symmetri Technology
dww volunteering
thetaPC
companyguy
adrianavaz
ex dj
das-peter
andres.torres
solide-echt organization(s): Solide BV
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.