Contribution records
Contributors

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

Give credit to everyone
sun sun
larowlan larowlan
mile23 Mile23
nick_schuch nick_schuch
berdir berdir
dawehner dereine volunteering
daffie daffie
jibran jibran volunteering
neclimdul neclimdul
phenaproxima phenaproxima
amateescu amateescu customer(s): Pfizer, Inc.
alexpott alexpott organization(s): Chapter Three (acquired by Kanopi Studios)
fgm fgm
pfrenssen pfrenssen
vijaycs85 vijaycs85
xano Xano
Crell Crell organization(s): Palantir.net
hussainweb hussainweb organization(s): Axelerant
fabianx Fabianx volunteering
naveenvalecha naveenvalecha volunteering organization(s): QED42
catch catch
benjy benjy organization(s): PreviousNext
chx chx
klausi klausi
wim leers wimleers organization(s): Acquia
tim.plunkett tim.plunkett organization(s): Acquia
kim.pepper kimpepper
hitesh-jain Hitesh88 organization(s): Acquia
neetu morwani neetumorwani 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.