Issue
Contribution records
Contributors

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

Give credit to everyone
xjm volunteering
fgm organization(s): OSInet
rachel_norfolk organization(s): Cambridge University Press & Assessment
asolero
chananiel
ekl1773 volunteering
ideaseed
LauraRocks volunteering organization(s): KMG Turku / KMG Digital
markhope organization(s): Access (now GAIN)
sugaroverflow
yesct organization(s): Lullabot customer(s): State of Georgia
ziomizar volunteering
andrewtur
colorfulcoder
cverde volunteering
giuseppe87
jhuhta organization(s): Siili Solutions
StelaOroz
wizonesolutions volunteering organization(s): WizOne Solutions customer(s): FillPDF Service
eric heydrich organization(s): werbeagentur kartinka gmbh & co. kg
norman.lol organization(s): 1xINTERNET
klara binon organization(s): VDAB
anna.radulovski
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.