Issue
Contribution records
Contributors

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

Give credit to everyone
frankcarey volunteering organization(s): DEVINCI
misc organization(s): Mearra (formerly known as Wunder)
cilefen
azinck
dhansen organization(s): Sevaa Group
danepowell organization(s): Acquia
dawehner organization(s): Chapter Three (acquired by Kanopi Studios)
serkanb organization(s): Bright Solutions GmbH
Toche volunteering
nikunjkotecha volunteering organization(s): Axelerant
jofitz organization(s): ComputerMinds
legolasbo organization(s): Deeson
borisson_ volunteering
LNakamura organization(s): Current
michfuer volunteering organization(s): Current
damiankloip organization(s): Acquia
mpdonadio organization(s): DiD Agency
lcatlett
fgm organization(s): OSInet
justafish organization(s): Lullabot
nplowman organization(s): JAKALA (formerly FFW)
tunic organization(s): Metadrop
rosk0 organization(s): Catalyst IT
oheller organization(s): Electric Citizen
weynhamz organization(s): CI&T
renrhaf organization(s): CGI customer(s): Ville de Montréal
julien organization(s): Code Enigma
jungle volunteering
tyler36
Git commit message
Commit types

Click on the types below to update the "Commit type" input.

  • 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
  • task: A planned operational or maintenance change to the codebase

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.