feat: add GitHub repository configuration and development workflow setup

Author: Bit-Maximum

.editorconfig

@@ -0,0 +1,16 @@
+[*.{kt,kts}]
+indent_size=4
+insert_final_newline = true
+ij_kotlin_imports_layout=*
+ktlint_code_style=intellij_idea
+ktlint_function_naming_ignore_when_annotated_with = Composable
+max_line_length = 120
+
+# Do not apply the general rule to generated files
+[**/generated/**/*.{kt,kts}]
+indent_size = unset
+max_line_length = unset
+insert_final_newline = unset
+
+[**/*{t,T}est/kotlin/**.kt]
+ktlint_standard_class-signature = disabled

.gitattributes

@@ -0,0 +1 @@
+*.java text eol=lf

.gitguardian.yml

@@ -0,0 +1,5 @@
+incident:
+  ignore:
+    - name: "Ignore example secrets"
+      match: "app/settings.py"
+      reason: "Example credentials that are not used in production."

.github/CONTRIBUTING.md

@@ -0,0 +1,58 @@
+# **Contributing**
+
+When contributing to this repository, please first discuss the change you wish to make via issue,
+chat, or any other method with the owners of this repository before making a change.
+
+## Git Flow
+
+The project uses the Git Flow branching model. The main branches are `main` and `develop`. The `main` branch is the production-ready branch, and the `develop` branch is the integration branch.
+
+The branches are used as follows:
+
+* From Feature to Feature: squash and merge
+* From Feature to Develop: squash and merge
+* From Develop to Main: fast-forward merge
+* From Main to Develop: fast-forward merge
+* From Hotfix to Main: fast-forward merge
+
+It's important to follow this flow to keep the project organized and to avoid conflicts.
+
+Every time a feature is merged into the `main` branch, a new release should be created with the version number following the [Semantic Versioning](https://semver.org/) guidelines.
+
+Also, the project uses pre-commit hooks to ensure the code quality. You should install them with `pre-commit install`.
+
+## Commits
+
+The project uses the [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) specification. This is a lightweight convention on top of commit messages. It provides an easy set of rules for creating an explicit commit history. This convention dovetails with [SemVer](https://semver.org/), by describing the features, fixes, and breaking changes made in commit messages.
+
+Each commit message should be conceptually unique and should be able to be understood by itself. It should only contain changes related to the name of the commit. If you need to make a commit with multiple changes that are independent (conceptually), you should split it into multiple commits.
+
+## Pull Request Process
+
+### Features
+
+1. Create your Feature Branch (`git checkout feature/{issue-number}-AmazingFeature`)
+2. Check that you have installed pre-commit hooks with `pre-commit install`.
+3. Check that your branch is up to date with `git pull` and merge if it's necessary with `git merge origin develop`.
+4. Commit your Changes (`git commit -m 'Add some AmazingFeature'`)
+5. Push to the Branch (`git push`)
+6. Open a Pull Request to the `develop` branch or to the main epic branch if there's one defined.
+
+### Bug Fixes
+
+Same as Features, but the branch name should be `bugfix/{issue-number}-FixingSomething`.
+
+### Hotfixes
+
+Same as Features, but the branch name should be `hotfix/{issue-number}-FixingSomething`. And the Pull Request should be opened to the `main` branch.
+
+## Issue Report Process
+
+1. Go to the project's issues.
+2. Select the template that better fits your issue.
+3. Read the instructions carefully and write within the template guidelines.
+4. Submit it and wait for support.
+
+## GitHub Projects
+
+You can use GitHub Projects to manage the project's tasks. It's a good way to keep track of the issues and pull requests.

.github/FUNDING.yml

@@ -0,0 +1 @@
+github: [Bit-Maximum]

.github/SECURITY.md

@@ -0,0 +1,56 @@
+# 🔒 Security Policy
+
+## Supported Versions
+
+| Version   | Supported          |
+|-----------|--------------------|
+| 1.x.x     | ✅                  |
+| <1.0.0    | ❌                  |
+
+---
+
+## Reporting a Vulnerability
+
+If you discover a security vulnerability, please **do not open a public issue**.
+Instead, report it via:
+
+- Email: security@example.com
+- GitHub Security Advisory: https://github.com/OWNER/REPO/security/advisories/new
+
+Include:
+- Description of the vulnerability
+- Steps to reproduce (or proof of concept)
+- Affected versions and environment details
+
+We aim to respond within **48 hours** and provide a fix or mitigation within **14 days**.
+
+---
+
+## Handling Secrets
+
+- **Never commit** `.env` or `.secrets` files with real credentials.
+- For example see `.env.example` and `.secrets.example` with placeholder values for environment variables.
+- In CI/CD (GitHub Actions), store secrets via **Settings → Secrets and variables**.
+- For local testing with **Act**, place credentials in `.secrets` (ignored by `.gitignore`).
+
+Example `.env.example`:
+```env
+DATABASE_URL=postgresql://username:password@localhost:5432/dbname
+SECRET_KEY=changeme
+```
+
+Example `.secrets.example`:
+```env
+DOCKERHUB_USERNAME=your-username
+DOCKERHUB_TOKEN=your-token
+```
+
+---
+
+### Security Best Practices
+- Keep dependencies updated (use Dependabot).
+- Scan code with security linters (Bandit, Ruff).
+- Use container vulnerability scanners (Trivy, Grype).
+- Avoid hardcoding API keys or passwords.
+
+---

.github/SUPPORT.md

@@ -0,0 +1,11 @@
+# **Support**
+
+## Obtain direct support from the project's owners
+
+1. Open a new issue and select the issue with the template called "❓ Question or Support Request".
+2. Read the instructions carefully in that template and submit the issue asking for support
+or any question.
+
+## Bug reports
+
+See the [contributing guidelines](CONTRIBUTING.md) for sharing bug reports.

.github/config.yml

@@ -0,0 +1,20 @@
+# Configuration for new-issue-welcome - https://github.com/behaviorbot/new-issue-welcome
+
+# Comment to be posted to on first time issues
+newIssueWelcomeComment: >
+  Thanks for opening your first issue! Be sure to follow the issue template and provide every bit of information to help the developers!
+
+# Configuration for new-pr-welcome - https://github.com/behaviorbot/new-pr-welcome
+
+# Comment to be posted to on PRs from first time contributors in your repository
+newPRWelcomeComment: >
+  Thanks for opening this pull request! Please check out our contributing guidelines and make sure to follow the pull request template.
+
+# Configuration for first-pr-merge - https://github.com/behaviorbot/first-pr-merge
+
+# Comment to be posted to on pull requests merged by a first time user
+firstPRMergeComment: >
+  Congrats on merging your first pull request! Keep making great things with us, thanks!!
+
+todo:
+  keyword: "@todo"

.github/dependabot.yml

@@ -0,0 +1,41 @@
+version: 2
+updates:
+  # GitHub Actions
+  - package-ecosystem: github-actions
+    directory: /
+    schedule:
+      interval: weekly
+    commit-message:
+      prefix: ⬆
+    labels:
+      - dependencies
+
+  # Java Gradle
+  - package-ecosystem: gradle
+    directory: /
+    schedule:
+      interval: weekly
+    commit-message:
+      prefix: ⬆
+    labels:
+      - dependencies
+
+  # Docker
+  - package-ecosystem: docker
+    directory: /
+    schedule:
+      interval: weekly
+    commit-message:
+      prefix: ⬆
+    labels:
+      - dependencies
+
+  # Docker Compose
+  - package-ecosystem: docker-compose
+    directory: /
+    schedule:
+      interval: weekly
+    commit-message:
+      prefix: ⬆
+    labels:
+      - dependencies

.github/labeler.yml

@@ -0,0 +1,60 @@
+documentation:
+  - all:
+    - changed-files:
+      - any-glob-to-any-file:
+        - '**/*.md'
+      - all-globs-to-all-files:
+        - '!src/**'
+        - '!.github/**'
+        - '!scripts/**'
+        - '!.gitignore'
+        - '!.pre-commit-config.yaml'
+
+ci/cd:
+  - all:
+    - changed-files:
+      - any-glob-to-any-file:
+        - ".github/**"
+        - "scripts/**"
+        - ".gitignore"
+        - ".pre-commit-config.yaml"
+        - ".gitlab-ci.yml"
+        - "alembic.ini"
+      - all-globs-to-all-files:
+        - '!./**/*.md'
+        - '!src/**'
+
+backend:
+  - all:
+    - changed-files:
+      - any-glob-to-any-file:
+        - "src/**"
+
+tests:
+  - all:
+    - changed-files:
+      - any-glob-to-any-file:
+        - "tests/**"
+
+docker:
+  - all:
+    - changed-files:
+      - any-glob-to-any-file:
+        - "deploy/**"
+        - "!deploy/kube/**"
+        - "Dockerfile"
+        - "docker-compose.yml"
+
+kubernetes:
+  - all:
+    - changed-files:
+      - any-glob-to-any-file:
+        - "deploy/kube/**"
+
+dependencies:
+  - all:
+    - changed-files:
+      - any-glob-to-any-file:
+        - ''
+      authors:
+        - "dependabot[bot]"