Contribution records
Contributors

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

Give credit to everyone
tduong tduong organization(s): MD Systems GmbH
berdir berdir organization(s): MD Systems GmbH
cilefen cilefen
andypost andypost volunteering organization(s): Skilld
timmillwood timmillwood organization(s): Appnovation customer(s): Pfizer, Inc.
joachim joachim
Bojhan bojhan volunteering
amateescu amateescu customer(s): Pfizer, Inc.
alexpott alexpott organization(s): Chapter Three (acquired by Kanopi Studios)
webchick webchick organization(s): Acquia
yoroy yoroy organization(s): Roy Scholten
ifrik ifrik
dawehner dereine volunteering organization(s): Chapter Three (acquired by Kanopi Studios)
xjm xjm organization(s): Acquia
twistor twistor volunteering
gábor hojtsy goba organization(s): Acquia
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.