Contribution records
Contributors

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

Give credit to everyone
kulmjens kulmjens organization(s): werk21
cilefen cilefen
christyanpaim christyanpaim organization(s): CI&T
sascha_meissner sascha_meissner organization(s): werk21
quietone quietone organization(s): PreviousNext
matthieuscarset matthieuscarset volunteering organization(s): Ecedi
smustgrave smustgrave organization(s): Mobomo
bessonweb besky
bernardm28 bernardm28 volunteering organization(s): Vaultes
dww dww volunteering
simohell simohell organization(s): Druid
rkoller rkoller
benjifisher benjifisher volunteering
blackbamboo BlackBamboo
skaught SKAUGHT organization(s): OPTASY
worldlinemine worldlinemine volunteering
xjm xjm organization(s): HeroDevs, xjm
longwave longwave organization(s): Full Fat Things
nod_ nod_ organization(s): Très Bien Tech
donquixote donquixote volunteering organization(s): European Commission and European Union Institutions, Agencies and Bodies
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.