Issue
Contribution records
Contributors

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

Give credit to everyone
wturrell volunteering
dawehner organization(s): Chapter Three (acquired by Kanopi Studios)
yoroy organization(s): Roy Scholten
vrwired
jmickela organization(s): Rootid
leolandotan volunteering organization(s): Promet Source
deckblad
lendude organization(s): iO
ranjith_kumar_k_u organization(s): Zyxware Technologies
smustgrave organization(s): Mobomo
quietone organization(s): PreviousNext
dcam volunteering
nod_ organization(s): Très Bien Tech customer(s): OpenSense Labs, OPTASY, Palantir.net, Vardot
catch organization(s): Third and Grove
igorgoncalves organization(s): ImageX
neilb@ed organization(s): The University of Edinburgh
chr.fritsch organization(s): Thunder
priyanka.sahni organization(s): Material customer(s): Drupal India Association
narendra.rajwar27 volunteering organization(s): Material customer(s): Drupal India Association
kristen pol organization(s): Itty Bitty Byte customer(s): Salsa Digital
sonam.chaturvedi organization(s): Salsa Digital
xjm organization(s): xjm, Zoocha
uesli organization(s): Zoocha
simohell organization(s): Druid
godotislate volunteering
mondrake
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.