Contribution records
Contributors

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

Give credit to everyone
dww dww volunteering
andypost andypost volunteering organization(s): Skilld
lendude Lendude organization(s): iO
alexpott alexpott organization(s): Thunder
klausi klausi organization(s): jobiqo - job board technology
pguillard pguillard
catch catch organization(s): Third and Grove
hardik_patel_12 Hardik_Patel_12 organization(s): Portage CyberTech, QED42 customer(s): Drupal India Association
mrinalini9 mrinalini9 organization(s): Material customer(s): Drupal India Association
mondrake mondrake volunteering
ridhimaabrol24 ridhimaabrol24 organization(s): Material customer(s): Drupal India Association
xjm xjm organization(s): Acquia
quietone quietone organization(s): PreviousNext
claudiu.cristea claudiucristea volunteering organization(s): Webikon
kim.pepper kimpepper organization(s): PreviousNext
manuel garcia manuelgarcia volunteering organization(s): Appnovation customer(s): Pfizer, Inc.
ravi.shankar ravi.shankar organization(s): OpenSense Labs
deepak goyal DeepakGoyal 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.