Issue
Contribution records
Contributors

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

Give credit to everyone
sam152
Bojhan
jibran volunteering
dawehner volunteering organization(s): Chapter Three (acquired by Kanopi Studios)
4aficiona2
naveenvalecha volunteering organization(s): Acquia customer(s): Acquia
swentel
mishradileep volunteering
dman volunteering organization(s): Sparks Interactive
gapple volunteering organization(s): Myplanet
andypost volunteering organization(s): Skilld
xjm
hkirsman
gmario
yoroy organization(s): Roy Scholten
feyp volunteering organization(s): werk21
esolitos organization(s): Ramsalt Lab
bircher organization(s): Nuvole
ifrik
fonski
yareckon customer(s): Ärzte ohne Grenzen e.V. / Médecins Sans Frontières
ckaotik organization(s): werk21
eric115 organization(s): PreviousNext
juusechec volunteering
dubcanada
ricovandevin organization(s): Finlet customer(s): One Shoe
pameeela volunteering
acbramley organization(s): PreviousNext
alexpott volunteering organization(s): Acro Commerce, Thunder
joelpittet organization(s): The University of British Columbia
nitesh pawar organization(s): Trigyn Technologies Ltd
wim leers organization(s): Acquia
kim.pepper
martijn de wit organization(s): Ablerz
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.