Issue
Contribution records
Contributors

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

Give credit to everyone
temoor
ohthehugemanatee
upchuk
rpayanm organization(s): SeeD EM
balagan
cilefen
filijonka
Poornima3
cosmicdreams
tstoeckler
pcambra
linl
unstatu
jeroent organization(s): iO
alexpott organization(s): Chapter Three (acquired by Kanopi Studios)
abhi170893
siva_epari
disasm organization(s): AppliedTrust
nlisgo
mile23
lauriii
Tebro
xjm organization(s): Acquia
pieterjanput organization(s): iO
heddn
Michael Hodge Jr
perennial.sky
dom.
Shivam Agarwal
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.