Issue
Contribution records
Contributors

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

Give credit to everyone
joelpittet organization(s): The University of British Columbia
berdir organization(s): MD Systems GmbH
fabianx organization(s): Tag1 Consulting, Inc.
thenchev organization(s): MD Systems GmbH
calebtr
xjm organization(s): Acquia, xjm
slashrsm organization(s): MD Systems GmbH
dawehner volunteering
andypost volunteering organization(s): Skilld
alexpott organization(s): Chapter Three (acquired by Kanopi Studios)
lauriii volunteering
agoradesign
paul_canning
darvanen volunteering
golddragon007 organization(s): European Commission and European Union Institutions, Agencies and Bodies, Petend
webflo organization(s): UEBERBIT GmbH
duaelfr volunteering organization(s): Happyculture
godotislate volunteering
smustgrave organization(s): Mobomo
acbramley organization(s): PreviousNext
star-szr volunteering
wim leers organization(s): Acquia
manuel garcia volunteering organization(s): Appnovation customer(s): Pfizer, Inc.
ravi.shankar organization(s): OpenSense Labs
quietone organization(s): PreviousNext
nod_ organization(s): Très Bien Tech customer(s): Palantir.net, Vardot
murz volunteering organization(s): EPAM customer(s): EPAM
plopesc organization(s): Lullabot customer(s): IndieCommerce - Website Development for Independent Booksellers
grevil organization(s): DROWL.de
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.