Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
myha
cilefen volunteering
mupsi volunteering
ironsizide organization(s): Message Agency
aaronbauman organization(s): Message Agency
catch organization(s): Third and Grove
greenskin volunteering
prudloff organization(s): Insite
pasqualle volunteering
smustgrave organization(s): Mobomo
giuseppe87
akalam
unstatu
gun_dose volunteering
andreic volunteering
gordonio organization(s): ImageX
ironnuts volunteering organization(s): Cactus Blossom IT Services Limited
niranjan_panem organization(s): Material
nod_ organization(s): Très Bien Tech customer(s): OpenSense Labs, OPTASY, Palantir.net, Vardot
the.tai.pen@gmail.com organization(s): JAKALA (formerly FFW)
claudiu.cristea volunteering organization(s): Webikon customer(s): European Commission and European Union Institutions, Agencies and Bodies
rajab natshah organization(s): Vardot customer(s): Vardot
ravi.shankar organization(s): OpenSense Labs
joaopauloc.dev organization(s): ImageX
carolpettirossi
mialdi98
acbramley organization(s): PreviousNext
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.