Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
znerol
fabianx volunteering organization(s): Tag1 Consulting, Inc.
larowlan volunteering
dawehner volunteering
mpdonadio organization(s): DiD Agency
borisson_ volunteering
hussainweb organization(s): Axelerant
deepakaryan1988 organization(s): Therefore
pwolanin volunteering organization(s): SciShield
vprocessor organization(s): Skilld
mile23 volunteering
voleger volunteering organization(s): Drupal Ukraine Community, GOLEMS GABB customer(s): Drupal Ukraine Community, GOLEMS GABB
yogeshmpawar volunteering organization(s): Portage CyberTech
daffie
andypost volunteering organization(s): Skilld
vladimiraus organization(s): Tomato Elephant Studio customer(s): Relationships Australia Queensland
afedoruk volunteering
dileepmaurya
izus
quietone volunteering
kingdutch organization(s): Open Social
wim leers organization(s): Acquia
gaurav.kapoor organization(s): OpenSense Labs
joseph.olstad
joachim
mradcliffe volunteering organization(s): Kosada
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.