Contribution records
Contributors

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

Give credit to everyone
fonant Fonant
tr tr
trevorbradley TrevorBradley
neograph734 Neograph734
grahamvalue grahamvalue
dimilias dimilias organization(s): Randstad Digital customer(s): European Commission and European Union Institutions, Agencies and Bodies
zread zread
garrettw garrettw organization(s): Encore Multimedia
cilefen cilefen
joos joos organization(s): WAPPO
interx interX volunteering organization(s): Anvil
sgdev ron_s
evaristo_colomby evaristo_colomby
andros andros
q11q11 q11 volunteering
jmaag jswitchback
jukka792 jukka792
rhip RhiP
bburg johnbburg organization(s): Forum One
hkirsman hkirsman
samhaldia samhaldia volunteering
torgospizza torgospizza
klausi klausi organization(s): jobiqo - job board technology
webdrips webdrips
sandykadam sandykadam
ñull com2 volunteering
stephane bouillet Stephane_Bouillet
Marko B MarkoBx
c-logemann C-Logemann organization(s): Nodegard
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.