Issue
Contribution records
Contributors

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

Give credit to everyone
damienmckenna organization(s): Current
tcnolan7
sashken2
timwright_
silverham organization(s): EY Digital
summit
la558
coufu
adriancotter
arcataroger
wylbur
jvogt volunteering
bondjimbond volunteering
niles38
skrossa volunteering organization(s): Stanford University
danbarron volunteering
alpe89
BrianLewisDesign
circuscowboy volunteering
chegor organization(s): OAO Solution Spark
emersonreis.dev organization(s): Zoocha
codebymikey organization(s): Zodiac Media
jedihe volunteering
ron collins organization(s): Affinity Bridge
Michael-IDA organization(s): Internet Design Alliance
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.