Contribution records
Contributors

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

Give credit to everyone
berdir berdir
droplet droplet
yched yched
Aeternum Aeternum
bluestarstudios bluestarstudios
marcingy marcingy
bartk lendrick
JamesK jkenn99
bkudrle bkudrle
karschsp karschsp
kking kking
webchick webchick
justindodge justindodge
attiks attiks
Gaelan Gaelan
aaronbauman aaronbauman organization(s): Message Agency
cweagans cweagans
alekth alekth
superspring superspring
thedavidmeister thedavidmeister
ao2 ao2 volunteering
dbyers55 dbyers55
OWast OskarWastensson organization(s): Happiness
dww dww volunteering
maticb maticb
alexpott alexpott organization(s): Acro Commerce, Thunder
quietone quietone organization(s): PreviousNext
alan d. aland
glass.dimly glassdimly
tim.plunkett tim.plunkett
sheldon rampton sheldon
stefan lehmann teppi
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.