Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
chrotto
dagmar organization(s): Globant
markot91 organization(s): Develomon customer(s): JAKALA (formerly FFW)
dawehner volunteering organization(s): Chapter Three (acquired by Kanopi Studios)
_Archy_ volunteering organization(s): PitechPlus
mschudders volunteering
pancho volunteering
nikita_tt volunteering
super_romeo volunteering
lendude volunteering organization(s): iO
playful
chankongching
ranjith_kumar_k_u organization(s): Zyxware Technologies
joelpittet organization(s): The University of British Columbia
quietone organization(s): PreviousNext
asad_ahmed organization(s): OpenSense Labs
ressa organization(s): Ardea
catch organization(s): Third and Grove
leducdubleuet
acbramley organization(s): PreviousNext
maxilein
espurnes organization(s): Sopra Steria
cilefen
jannakha
tonytheferg
karlshea
Ben Greenberg
sarguna raj m volunteering
ramil g organization(s): The University of British Columbia
akram khan volunteering organization(s): Material customer(s): Drupal India Association
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.