Issue
Contribution records
Contributors

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

Give credit to everyone
dsnopek
webchick organization(s): Acquia
phenaproxima organization(s): Acquia
johnkennedy
tstoeckler volunteering
dead_arm organization(s): Palantir.net
WidgetsBurritos organization(s): Rackspace
yoroy organization(s): Roy Scholten
skaught volunteering
tedbow organization(s): Acquia
neclimdul
dawehner organization(s): Chapter Three (acquired by Kanopi Studios)
zaporylie organization(s): Ny Media AS
dyannenova organization(s): Acquia
amateescu customer(s): Pfizer, Inc.
xjm organization(s): Acquia
larowlan organization(s): PreviousNext
eclipsegc organization(s): Acquia
markhalliwell organization(s): Tag1 Consulting, Inc.
damienmckenna organization(s): Current
ipwa
samuel.mortenson organization(s): Acquia
gábor hojtsy organization(s): Acquia
tim.plunkett organization(s): Acquia
manuel garcia volunteering organization(s): Appnovation customer(s): Pfizer, Inc.
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.