### Example Git Commit Message Format

Source: https://github.com/mpos/php-mpos/blob/master/CONTRIBUTING.md

This snippet provides an example of the recommended format for Git commit messages in this project. It includes a concise subject line starting with an issue number and an imperative verb, followed by a detailed body explaining the problem and the solution.

```git commit
    (#99999) Make the example in CONTRIBUTING imperative and concrete

    Without this patch applied the example commit message in the CONTRIBUTING
    document is not a concrete example.  This is a problem because the
    contributor is left to imagine what the commit message should look like
    based on a description rather than an example.  This patch fixes the
    problem by making the example concrete and imperative.

    The first line is a real life imperative statement with an issue number
    from our issue tracker.  The body describes the behavior without the patch,
    why this is a problem, and how the patch fixes the problem when applied.
```

--------------------------------

### Add Test Suite to phpunit.xml (XML)

Source: https://github.com/mpos/php-mpos/blob/master/tests/README.md

This XML snippet defines a test suite named 'SampleTest' that includes all test files within the 'unit/config' directory. This entry should be added to the project's phpunit.xml configuration file to include the tests in the suite.

```xml
<testsuite name="SampleTest">
  <directory>unit/config</directory>
</testsuite>
```

--------------------------------

### Run PHPUnit Unit Tests (Bash)

Source: https://github.com/mpos/php-mpos/blob/master/tests/README.md

Execute the unit tests located in the 'tests/unit' directory using the PHPUnit command-line runner. This command initiates the test execution process.

```bash
phpunit tests/unit
```

--------------------------------

### Configuring SSO Shared Database and Cookie Domain in MPOS

Source: https://github.com/mpos/php-mpos/blob/master/CHANGELOG.md

These configuration options, introduced in MPOS 1.0.2, enable Single Sign-On (SSO) across multiple MPOS pools. They allow specifying shared database tables for accounts, workers, and news, and require setting a common cookie domain for all participating pools.

```PHP
$config['db']['shared']['acounts']; // defaults to $config['db']['name']
$config['db']['shared']['workers']; // defaults to $config['db']['name']
$config['db']['shared']['news'];    // defaults to $config['db']['name']
$config['cookie']['domain'];        // Required for SSO, use top-level domain (e.g., .thepool.com)
```

=== COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.