Contribution records
Contributors

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

Give credit to everyone
mgifford mgifford organization(s): OpenConcept Consulting Inc.
swentel swentel
andymartha biolithic
Bojhan bojhan
cwarsaw cwarsaw
bowersox brandonojc
jessebeach jessebeach volunteering
nod_ nod_
falcon03 falcon03
aaronbauman aaronbauman
sun sun
xjm xjm organization(s): Acquia
alexpott alexpott
mpdonadio matthew.donadio organization(s): DiD Agency
rteijeiro rteijeiro organization(s): Tieto
vprocessor vprocessor organization(s): Skilld
andypost andypost volunteering organization(s): Skilld
yoroy yoroy organization(s): Roy Scholten
jhedstrom jhedstrom organization(s): Phase2 customer(s): Workday, Inc.
sjpeters79 sjpeters79
cilefen cilefen
sugaroverflow sugaroverflow
drumm drumm organization(s): Drupal Association
lauriii lauriii organization(s): Druid
tim bozeman boze
r.nabiullin r.nabiullin organization(s): Skilld
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.