Issue
Contribution records
Contributors

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

Give credit to everyone
rkoller
benjifisher volunteering organization(s): Harvard Web Publishing
dww volunteering
emma horrell organization(s): The University of Edinburgh
lauriii
the_g_bomb volunteering
berdir organization(s): MD Systems GmbH
hooroomoo organization(s): Acquia
poker10 organization(s): ActivIT s.r.o.
hudri organization(s): webtourismus.at
marcoscano volunteering organization(s): Lullabot
tstoeckler organization(s): resc.
ifrik volunteering
joachim volunteering
yoroy organization(s): Roy Scholten
arpitr
chris matthews
asherry volunteering
bernardm28 volunteering organization(s): Vaultes
dydave organization(s): Code Enigma
h2cm volunteering
mr_scumbag organization(s): Code Journeymen customer(s): Code Journeymen
philipnorton42 organization(s): #! code (Hash Bang Code), Code Enigma
drubb organization(s): arocom GmbH
franz-m volunteering
jurgenhaas organization(s): LakeDrops customer(s): OPTASY
martin mayer volunteering
cedewey volunteering organization(s): DevCollaborative, LLC
jannafiester
joannajackson
simohell organization(s): Druid
matthews volunteering organization(s): amazee.io, James Matthew Saunders LLC
treevis
timurtripp
longwave organization(s): Full Fat Things
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.