Issue
Contribution records
Contributors

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

Give credit to everyone
sandeepguntaka organization(s): Azri Solutions
jidrone organization(s): Mobomo customer(s): Vibrent Health
amateescu customer(s): Pfizer, Inc.
berdir organization(s): MD Systems GmbH
lobsterr organization(s): European Commission and European Union Institutions, Agencies and Bodies
kingdutch organization(s): Open Social
scotwith1t organization(s): Mobomo
jwilson3 organization(s): Bluespark
kristiaanvandeneynde organization(s): Factorial.io customer(s): Global Game Jam
taylormade415 volunteering
attiks organization(s): Attiks customer(s): United Nations
brooke_heaton volunteering
gorkagr organization(s): Erasmus Student Network
devkinetic organization(s): CommonPlaces Interactive
ridhimaabrol24 organization(s): Material customer(s): Drupal India Association
marty2081 organization(s): ronder
edysmp organization(s): MTech, LLC
heddn organization(s): MTech, LLC, Tag1 Consulting, Inc.
lahode
zcht
jaypan
jnicola organization(s): Oregon Health & Science University (OHSU)
pianomansam organization(s): Rapid Development Group
jellyburger
laura.gates
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.