Merge branch 'release'

.gitattributes

@@ -2,16 +2,14 @@
 
 /.github                export-ignore
 /tests                  export-ignore
-/.dockerignore          export-ignore
 /.editorconfig          export-ignore
-/.env.example           export-ignore
 /.gitattributes         export-ignore
 /.gitignore             export-ignore
 /.php-cs-fixer.php      export-ignore
 /composer.lock          export-ignore
-/docker-compose.yaml    export-ignore
 /phpstan-baseline.neon  export-ignore
 /phpstan.neon           export-ignore
 /phpunit.xml            export-ignore
 /psalm-baseline.xml     export-ignore
 /psalm.xml              export-ignore
+/clover.xml             export-ignore

.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,128 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+.
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior,  harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.0, available at
+https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct
+enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at
+https://www.contributor-covenant.org/translations.

.github/CONTRIBUTING.md

@@ -0,0 +1,21 @@
+# How to Contribute
+
+## Pull Requests
+
+1. Fork the ModernPDO repository
+2. Create a new branch for each action ("feature/***branch_name***" or "bugfix/***branch_name***")
+3. Send a pull request from each of your branches to the "develop" branch
+
+It is very important because ModernPDO follows Gitflow.
+
+## Style Guide
+
+Before a pull request you must run `composer csfix` to fix the code style.
+
+## Testing
+
+All pull requests must be accompanied by passing unit/integration tests and static analyzes.
+
+#### We use:
+- [PHPUnit](https://github.com/sebastianbergmann/phpunit) for unit/integration tests.
+- [PHPStan](https://github.com/phpstan/phpstan) and [PSalm](https://github.com/vimeo/psalm) for static analyzes.

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,31 @@
+name: Bug Report
+description: Create a bug report
+labels: ["bug"]
+body:
+  - type: textarea
+    attributes:
+      label: Description
+      description: "Please provide a description and way to reproduce the problem."
+    validations:
+      required: true
+  - type: input
+    attributes:
+      label: ModernPDO Version
+      description: "The ModernPDO version used."
+      placeholder: "3.0.0"
+    validations:
+      required: true
+  - type: input
+    attributes:
+      label: DBMS
+      description: "The DBMS name and version used, if needed."
+      placeholder: "MariaDB v10.5"
+    validations:
+      required: false
+  - type: input
+    attributes:
+      label: PHP Version
+      description: "The php version used, if needed."
+      placeholder: "8.1"
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1 @@
+blank_issues_enabled: false

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,10 @@
+name: Feature Request
+description: Create a feature request
+labels: ["enhancement"]
+body:
+  - type: textarea
+    attributes:
+      label: Description
+      description: "Please provide a description of the feature or enhancement."
+    validations:
+      required: true

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,7 @@
+<!---
+
+Please describe the reason for the changes you're proposing. If it is a large change, please open an issue to discuss first.
+
+Always follow the [contribution guidelines](https://github.com/StulE-ru/ModernPDO/tree/main/.github/CONTRIBUTING.md) when submitting a pull request. In particular, make sure existing tests still pass, and add tests for all new behavior. When fixing a bug, you may want to add a test to verify the fix.
+
+-->

.github/SECURITY.md

@@ -0,0 +1,26 @@
+# Security Policy
+
+## Supported Versions
+
+We support fixing security issues on the following releases:
+
+| Version | Supported          | Security fixes until
+| ------- | ------------------ | --------------------
+| 3.x.x   | :white_check_mark: | 3 Months after the release of 4.0.0
+| 2.x.x   | :x:                | No longer supported
+| 1.x.x   | :x:                | No longer supported
+
+## Reporting a Vulnerability
+
+If you’ve found a security issue in ModernPDO, please use the following procedure
+instead of the normal bug reporting system. Send a message to the [owner](https://t.me/nnp666) in telegram.
+
+For each report, we try to first confirm the vulnerability. Once confirmed,
+the ModernPDO team will take the following actions:
+
+* Acknowledge to the reporter that we’ve received the issue, and are
+  working on a fix. We ask that the reporter keep the issue confidential until we announce it.
+* Get a fix/patch prepared.
+* Prepare a post describing the vulnerability, and the possible exploits.
+* Release new versions of all affected versions.
+* Prominently feature the problem in the release announcement