Issue
Contribution records
Contributors

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

Give credit to everyone
gillesv
vivekguptakota organization(s): Faichi Solutions Pvt Ltd customer(s): Faichi Solutions Pvt Ltd
segovia94 volunteering
Saphyel organization(s): Comic Relief
heikkiy
xjm organization(s): Acquia
tstoeckler volunteering
dpacassi volunteering
ayalon organization(s): Liip
acbramley organization(s): PreviousNext customer(s): Transport for NSW
cristian100
sam152 volunteering organization(s): PreviousNext
vijaycs85 volunteering organization(s): Solathat, TATA Consultancy Services customer(s): Pfizer, Inc.
flocondetoile organization(s): Flocon de toile
florianmuellerch volunteering
matthiasm11 organization(s): Randstad Digital
timwood
dead_arm organization(s): Palantir.net
oriol_e9g organization(s): Diputació de Barcelona
grantkruger
firewaller
badjava organization(s): Metasun customer(s): Pfizer, Inc.
mrpauldriver
rupesh_jagtap volunteering
c13l0 volunteering
screon
juhog organization(s): Druid customer(s): Lääkärikeskus Aava Oy
wim leers organization(s): Acquia
nvaken
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.