Issue
Contribution records
Contributors

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

Give credit to everyone
g4mbini organization(s): Alliance of Digital Builders (AODB), Dropteam
dhansen organization(s): Sevaa Group
echechulina organization(s): Kanopi Studios
grimreaper organization(s): Smile
janes_p volunteering
juc1
kerrymick organization(s): Kanopi Studios
laetitia_al organization(s): Smile
mherchel volunteering organization(s): Dripyard customer(s): OPTASY
mogtofu33 volunteering organization(s): Beyris
monet-fort volunteering
nkarhoff organization(s): Kanopi Studios
nod_ volunteering organization(s): Très Bien Tech customer(s): OPTASY, Palantir.net, Vardot
opantoja organization(s): DigitalProjex
osman_seferov
pdureau volunteering
rajab natshah organization(s): Vardot customer(s): Vardot
raluelrusu volunteering
sea2709 organization(s): Portland Webworks
shanekba
yannickoo organization(s): 1xINTERNET
_izaac volunteering
pabst_blue_ribbon
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.