Contribution records
Contributors

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

Give credit to everyone
andregp andregp
rkoller rkoller
ifrik ifrik volunteering
glynster glynster
tgoeg tgoeg
mherchel mherchel
nayana_mvr Nayana_R organization(s): Material
quietone quietone organization(s): PreviousNext
catch catch organization(s): Third and Grove
frega frega volunteering
Reinmar Reinmar
saidatom saidatom organization(s): Squarebit customer(s): European Commission and European Union Institutions, Agencies and Bodies
lauriii lauriii organization(s): Acquia
joshuautley joshuautley
burnellw_cit burnellw_cit
murphyw murphyW
sir_squall sir_squall
solideogloria solideogloria
jessey jessey
dom. Miroslav volunteering organization(s): ACINO
wim leers wimleers organization(s): Acquia
geek-merlin geek-merlin organization(s): Geeks4Change, MachbarMacher
claudiu.cristea claudiucristea volunteering organization(s): Webikon customer(s): European Commission and European Union Institutions, Agencies and Bodies
nitin shrivastava Nitin_shrivastava organization(s): OpenSense Labs
star-szr star-szr organization(s): Consensus Enterprises customer(s): Ontario Digital Service
leo liao leoliaobo
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.