Contribution records
Contributors

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

Give credit to everyone
timmillwood timmillwood organization(s): Appnovation customer(s): Pfizer, Inc.
alexpott alexpott organization(s): Chapter Three (acquired by Kanopi Studios)
catch catch organization(s): Third and Grove
scookie scookie organization(s): Workday, Inc.
sam152 sam volunteering organization(s): PreviousNext
pericxc pericxc
jibran jibran volunteering
jhedstrom jhedstrom organization(s): Phase2 customer(s): Workday, Inc.
tacituseu tacituseu
bojanz bojanz organization(s): Centarro
amateescu amateescu customer(s): Pfizer, Inc.
fabianx Fabianx volunteering
tstoeckler tstoeckler volunteering organization(s): bio.logis Genetic Information Management GmbH
xjm xjm organization(s): Acquia
yoroy yoroy organization(s): Roy Scholten
jojototh mogdesign organization(s): Pfizer, Inc.
tr tr
cilefen cilefen volunteering
nlisgo nlisgo
gábor hojtsy goba organization(s): Acquia
samuel.mortenson samuel.mortenson 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.