Issue
Contribution records
Contributors

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

Give credit to everyone
solotandem
ayesh
mikeytown2
sjerdo volunteering
nwom
cezkid
maximpodorov
fabianx volunteering organization(s): Tag1 Consulting, Inc.
tshorock
mcdruid
gary_mazz volunteering
truls1502 volunteering
farnoosh volunteering
rgpublic
oriol_e9g organization(s): Diputació de Barcelona
apotek
pipicom
raushan
mrgoodfellow
mustanggb
gnurob
pramodini123
pol organization(s): Arhs customer(s): European Commission and European Union Institutions, Agencies and Bodies
bruhnrp
ydahi
pounard
travelvc volunteering
tbadaczewski
damienmckenna organization(s): Current
brianlp
axle_foley00
joseph.olstad
rob c
Adam Neutrik volunteering
Pablo Gosse volunteering
martijn de wit organization(s): Ablerz
El Bandito volunteering
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.