Add solution folders, workflows, and configuration files for CI/CD, code coverage, and contribution guidelines

Author: selcukgural

.gitattributes

@@ -0,0 +1,12 @@
+# .gitattributes for SGuard.DataAnnotations
+# Ensure consistent line endings and text encoding
+* text=auto
+*.cs diff=csharp
+*.resx text
+*.md text
+*.yml text
+*.json text
+*.sln text
+*.csproj text
+*.runsettings text
+

.github/BRANCH_NAMING_GUIDLINES.md

@@ -0,0 +1,39 @@
+# Branch Naming Guidelines
+
+When creating a new branch, please follow this naming convention to maintain consistency and clarity in communication regarding the nature of changes.
+
+## Protected Branches
+
+These branches are protected and can only be updated by repository administrators. As a contributor, do **not** commit directly to these branches.
+
+| Branch Name | Description                                                                            |
+| ----------- | -------------------------------------------------------------------------------------- |
+| `main`      | The stable, production-ready version of the website.                                   |
+| `dev`       | The development branch containing features and bug fixes not yet ready for production. |
+
+## Contributing Branches
+
+These branches are open for contributions from all contributors. Follow these naming conventions when creating a new branch:
+
+| Branch Name  | Description                                                                                            |
+| ------------ | ------------------------------------------------------------------------------------------------------ |
+| `feat/x`     | A branch for adding new features or enhancing functionality. Replace `x` with a short description.     |
+| `fix/x`      | A branch for fixing bugs. Replace `x` with a description of the issue being addressed.                 |
+| `docs/x`     | A branch for documentation updates. Replace `x` with a description of the documentation being updated. |
+| `style/x`    | A branch for code style changes (formatting, spacing, etc.). Replace `x` with the style change.        |
+| `refactor/x` | A branch for code refactoring that doesn’t change functionality. Replace `x` with a description.       |
+| `perf/x`     | A branch for performance improvements. Replace `x` with the specific performance enhancement.          |
+| `test/x`     | A branch for adding or modifying tests. Replace `x` with the test being added or modified.             |
+| `chore/x`    | A branch for routine tasks or maintenance (e.g., upgrading dependencies). Replace `x` with the task.   |
+
+## Examples
+
+Here are a few examples of valid branch names:
+
+- `feat/navbar` - New feature for the navbar.
+- `fix/login` - Bug fix for the login functionality.
+- `docs/readme` - Update to the README documentation.
+- `style/formatting` - Code style formatting changes.
+- `refactor/database` - Refactor the database connection handling.
+- `test/authentication` - Tests for the authentication service.
+- `chore/dependencies` - Update dependencies.

.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,43 @@
+# .NET Foundation Code of Conduct
+
+This project has adopted the code of conduct defined by the .NET Foundation to foster an open and welcoming environment for contributors and users.
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to make participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment include:
+- Using welcoming and inclusive language
+- Being respectful of differing viewpoints and experiences
+- Gracefully accepting constructive criticism
+- Focusing on what is best for the community
+- Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+- The use of sexualized language or imagery and unwelcome sexual attention or advances
+- Trolling, insulting/derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or electronic address, without explicit permission
+- Other conduct, which could reasonably be considered inappropriate in a professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at [selcukgural@gmail.com]. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org/version/2/0/code_of_conduct/) and the .NET Foundation Code of Conduct.
+
+---
+
+For more information, see the [.NET Foundation Code of Conduct](https://dotnetfoundation.org/about/code-of-conduct).

.github/CONTRIBUTING.md

@@ -0,0 +1,41 @@
+# Contributing to SGuard.DataAnnotations
+
+Thank you for your interest in contributing to SGuard! We welcome contributions from everyone. This guide will help you get started.
+
+## How to Contribute
+
+1. **Fork the repository**
+    - Click the "Fork" button at the top of the GitHub page to create your own copy.
+2. **Clone your fork**
+    - `git clone https://github.com/selcukgural/SGuard.DataAnnotations.git`
+3. **Create a branch**
+    - `git checkout -b my-feature-branch`
+4. **Make your changes**
+    - Add your improvements, bug fixes, or documentation updates.
+5. **Test your changes**
+    - Ensure all tests pass and your code is robust.
+6. **Commit and push**
+    - `git commit -am "Describe your change"`
+    - `git push origin my-feature-branch`
+7. **Open a Pull Request**
+    - Go to your fork on GitHub and click "New Pull Request."
+
+## Code Style
+- Follow .NET and C# best practices.
+- Write clear, concise, and well-documented code.
+- Add XML comments for public APIs.
+
+## Reporting Issues
+- Use GitHub Issues to report bugs, request features, or ask questions.
+- Please provide as much detail as possible.
+
+## Community Standards
+- Be respectful and inclusive.
+- Follow the [Code of Conduct](CODE_OF_CONDUCT.md).
+
+## License
+By contributing, you agree that your contributions will be licensed under the MIT License.
+
+---
+
+Thank you for helping make SGuard.DataAnnotations better!

.github/FUNDING.yml

@@ -0,0 +1,4 @@
+# Example: Enable GitHub Sponsors
+# github: [your-github-username]
+# open_collective: your-collective
+

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,29 @@
+---
+name: Bug report
+about: Create a report to help us improve
+labels: bug
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Environment (please complete the following information):**
+ - OS: [e.g. Windows, macOS, Linux]
+ - .NET version:    [6.0, 7.0, 8.0, 9.0]
+ - Library version: [e.g. 1.0.0]
+
+**Additional context**
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,31 @@
+---
+name: Feature request
+about: Suggest an idea or improvement for this project
+labels: enhancement
+---
+
+**Where to open feature requests:**
+Please open feature requests at [the GitHub issue page](https://github.com/selcukgural/SGuard.DataAnnotations/issues/new/choose).
+
+**Contact:**
+For urgent or sensitive feature discussions, you can also contact the maintainer at selcukgural@gmail.com.
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. For example, "I'm always frustrated when..."
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen. If possible, provide example code or usage scenarios.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context, screenshots, or references (e.g., links to similar features in other libraries) about the feature request here.
+
+**Who would benefit from this feature?**
+Describe the target users or scenarios that would benefit from this feature.
+
+**Are you willing to help implement this feature?**
+- [ ] Yes
+- [ ] No
+- [ ] Maybe (please explain)

.github/ISSUE_TEMPLATE/feedback.md

@@ -0,0 +1,21 @@
+---
+name: 📢 Feedback
+about: Provide feedback for this project
+title: "📢 Feedback: Enter a short description of the issue"
+labels: "feedback"
+assignees: "dileepadev"
+---
+
+## 📢 Feedback
+
+### 📜 Description
+
+<!-- [REQUIRED] Briefly describe the feedback. -->
+
+### 🔗 Related Issues or PRs
+
+<!-- [OPTIONAL] Link to any related issues or pull requests. Remove if not needed. -->
+
+### 📝 Additional Information
+
+<!-- [OPTIONAL] Any additional context about the feedback here. Remove if not needed. -->

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,27 @@
+# Pull Request
+
+Thank you for your contribution!
+
+## Description
+Please provide a detailed summary of your changes, including:
+- The motivation and context for the change
+- The main functionality or fix introduced
+- Any relevant design decisions or architectural changes
+- References to related issues (e.g. Fixes #123)
+- Impact on existing code, APIs, or documentation
+- If applicable, describe how this aligns with .NET best practices (e.g. naming conventions, exception handling, extensibility, testability)
+
+## Type of change
+- [ ] Bug fix
+- [ ] New feature
+- [ ] Breaking change
+- [ ] Documentation update
+
+## Checklist
+- [ ] My code follows the style guidelines of this project
+- [ ] I have performed a self-review of my own code
+- [ ] I have commented my code, particularly in hard-to-understand areas
+- [ ] I have made corresponding changes to the documentation
+- [ ] My changes generate no new warnings
+- [ ] I have added tests that prove my fix is effective or that my feature works
+- [ ] New and existing unit tests pass locally with my changes

.github/SECURITY.md

@@ -0,0 +1,39 @@
+# Security Policy
+
+The [community](https://github.com/selcukgural/SGuard.DataAnnotations) project team takes security issues very seriously. We appreciate your efforts to responsibly disclose any security vulnerabilities you find.
+
+## Reporting a Vulnerability
+
+If you discover a security vulnerability, please email **<selcukgural@gmail.com>**. Please do not create a public issue for the vulnerability.
+
+Your email should include the following information:
+
+- A description of the vulnerability
+- Steps to reproduce the vulnerability
+- Possible impact of the vulnerability
+- Any suggested mitigation or remediation steps
+
+We will respond to your email as soon as possible and work with you to address any security issues.
+
+## Bug Bounty Program
+
+At this time, we do not offer a bug bounty program. If we decide to introduce one in the future, details will be shared here.
+
+## Maintainer Responsibilities
+
+Maintainers are responsible for the security of the project. This includes:
+
+- Responding to security reports in a timely manner
+- Investigating reported vulnerabilities
+- Developing and releasing patches for confirmed vulnerabilities
+- Communicating with the reporting party as the issue is addressed
+- Regularly reviewing and auditing the security of the project
+
+## Disclosures
+
+- We will acknowledge receipt of your report within one business day as soon as possible.
+- We will confirm the vulnerability and determine its impact.
+- We will release a fix as soon as possible, depending on the complexity of the issue.
+- We will communicate the vulnerability and any patches or workarounds to our users.
+
+Thank you for your help in making the [community](https://github.com/selcukgural/SGuard.DataAnnotations) project a more secure place.