Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
extexan
jonathanshaw
swentel organization(s): eps & kaas customer(s): MuseScore
cilefen
tacituseu
joelpittet organization(s): The University of British Columbia
coecks
scuba_fly organization(s): ronder
lukasss
puregin volunteering
acbramley organization(s): PreviousNext customer(s): Transport for NSW
Lloyd_87
andzejsw volunteering
maximpodorov
rgpublic
sime organization(s): Lil Engine
berdir
guillaumeduveau
gorkagr organization(s): Erasmus Student Network
malcomio organization(s): Capgemini
jastraat organization(s): CivicActions customer(s): Centers for Medicare and Medicaid Services
smustgrave
alan d.
ro-no-lo
pritam.tiwari volunteering
dom. volunteering organization(s): ACINO
shashwat purav organization(s): QED42 customer(s): Drupal Association
andypost volunteering organization(s): Skilld
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.