Issue
Contribution records
Contributors

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

Give credit to everyone
naveenvalecha volunteering
lomasr organization(s): gai Technologies Pvt Ltd customer(s): gai Technologies Pvt Ltd
dawehner volunteering organization(s): Chapter Three (acquired by Kanopi Studios)
chi
andypost volunteering organization(s): Skilld
daffie
larowlan organization(s): PreviousNext
vacho organization(s): Skilld
Mixologic organization(s): Drupal Association
thalles organization(s): CI&T
jhodgdon
catch organization(s): Third and Grove
aaronmchale organization(s): The University of Edinburgh
benjifisher
jrockowitz volunteering organization(s): The Big Blue House
webchick organization(s): Acquia
danielveza organization(s): PreviousNext
xjm organization(s): Agileana
sergiogsanchez organization(s): Agileana
quietone organization(s): PreviousNext
ravi.shankar organization(s): OpenSense Labs
gnanagowthaman sankar volunteering organization(s): UniMity Solutions Pvt Limited customer(s): UniMity Solutions Pvt Limited
neslee canil pinto organization(s): Specbee
gábor hojtsy organization(s): Acquia
gaurav-mathur organization(s): Dotsquares Ltd.
sahil.goyal volunteering organization(s): Material customer(s): Drupal India Association
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.