✨ feat(smee): add smee support (#7)

## 💌 Description

smee support

## 🔗 Related issue

<!-- If your PR refers to a related issue, link it here. -->
Fixes: #

## 🏗️ Type of change

<!-- Mark with an `x` all the checkboxes that apply (like `[x]`) -->

- [ ] 📚 Examples / docs / tutorials / dependencies update
- [ ] 🐛 Bug fix (non-breaking change which fixes an issue)
- [ ] 🥂 Improvement (non-breaking change which improves an existing
feature)
- [x] 🚀 New feature (non-breaking change which adds functionality)
- [ ] 💥 Breaking change (fix or feature that would cause existing
functionality to change)
- [ ] 🚨 Security fix
- [ ] ⬆️ Dependencies update

## ✅ Checklist

<!-- Mark with an `x` all the checkboxes that apply (like `[x]`) -->

- [x] I've read the [`Code of
Conduct`](https://github.com/DariuszPorowski/ghaction-dump-contexts/blob/main/.github/CODE_OF_CONDUCT.md)
document.
- [x] I've read the
[`Contributing`](https://github.com/DariuszPorowski/ghaction-dump-contexts/blob/main/.github/CONTRIBUTING.md)
guide.

Author: DariuszPorowski

.github/CODEOWNERS

@@ -1,2 +1,2 @@
 # Default reviewers/codeowners for all code changes in the repository
-* @DariuszPorowski
+* @raven-actions/reviewers

.github/CODE_OF_CONDUCT.md

@@ -14,11 +14,11 @@ Examples of behavior that contributes to a positive environment for our communit
 - 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's best not just for us as individuals, but for the overall community
+- Focusing on what's 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
+- 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
@@ -28,17 +28,17 @@ Examples of unacceptable behavior include:
 
 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.
+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 with 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.
+This Code of Conduct applies within all community spaces and when an individual officially represents the community in public spaces. Representing our community includes 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 [Twitter message](https://twitter.com/DariuszPorowski). All complaints will be reviewed and investigated promptly and fairly.
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for the enforcement at [LinkedIn message](https://www.linkedin.com/in/DariuszPorowski). 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.
+All community leaders must respect the privacy and security of the reporter of any incident.
 
 ## 🛂 Enforcement Guidelines
 
@@ -54,7 +54,7 @@ Community leaders will follow these Community Impact Guidelines in determining t
 
 **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.
+**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 and external channels like social media. Violating these terms may lead to a temporary or permanent ban.
 
 ### 3. Temporary Ban
 

.github/CONTRIBUTING.md

@@ -16,7 +16,7 @@ To contribute, please follow these steps:
 
 ## 🔰 Code of Conduct
 
-All contributors are expected to adhere to the project name code of conduct. Therefore, please review it before contributing [`Code of Conduct`](./CODE_OF_CONDUCT.md).
+All contributors are expected to adhere to the project name code of conduct. Therefore, please review it before contributing [`Code of Conduct`](https://github.com/raven-actions/dump-contexts/blob/main/.github/CODE_OF_CONDUCT.md).
 
 ## 📄 License
 

.github/ISSUE_TEMPLATE/bug.yml

@@ -1,5 +1,5 @@
----
 # https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema
+---
 name: 🐛 Bug Report
 description: If something isn't working 🔧
 title: "🐛 [bug]: "
@@ -82,7 +82,7 @@ body:
     id: terms
     attributes:
       label: 📜 Code of Conduct
-      description: By submitting this issue, you agree to follow our [`Code of Conduct`](https://github.com/DariuszPorowski/ghaction-dump-contexts/blob/main/.github/CODE_OF_CONDUCT.md)
+      description: By submitting this issue, you agree to follow our [`Code of Conduct`](https://github.com/raven-actions/dump-contexts/blob/main/.github/CODE_OF_CONDUCT.md)
       options:
         - label: I agree to follow this project's Code of Conduct.
           required: true

.github/ISSUE_TEMPLATE/config.yml

@@ -1,2 +1,7 @@
 # https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository#configuring-the-template-chooser
+---
 blank_issues_enabled: false
+# contact_links:
+#   - name: Support
+#     url: https://www.linkedin.com/in/DariuszPorowski
+#     about: Request support

.github/ISSUE_TEMPLATE/feature-request.yml

@@ -1,5 +1,5 @@
----
 # https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema
+---
 name: 🚀 Feature request
 description: Suggest an idea for this project 🏖
 title: "🚀 [feature]: "
@@ -44,7 +44,7 @@ body:
     id: terms
     attributes:
       label: 📜 Code of Conduct
-      description: By submitting this issue, you agree to follow our [`Code of Conduct`](https://github.com/DariuszPorowski/ghaction-dump-contexts/blob/main/.github/CODE_OF_CONDUCT.md)
+      description: By submitting this issue, you agree to follow our [`Code of Conduct`](https://github.com/raven-actions/dump-contexts/blob/main/.github/CODE_OF_CONDUCT.md)
       options:
         - label: I agree to follow this project's Code of Conduct.
           required: true

.github/ISSUE_TEMPLATE/question.yml

@@ -1,5 +1,5 @@
----
 # https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema
+---
 name: ❓ Question
 description: Ask a question about this project 🎓
 title: "❓ [question]: "
@@ -14,7 +14,7 @@ body:
       label: ✅ Checklist
       description: Mark with an ✔️ all the checkboxes that apply.
       options:
-        - label: I've searched the project's [`issues`](https://github.com/DariuszPorowski/ghaction-dump-contexts/issues?q=is%3Aissue) and did not find answer for my question.
+        - label: I've searched the project's [`issues`](https://github.com/raven-actions/dump-contexts/issues?q=is%3Aissue) and did not find answer for my question.
           required: true
   - type: textarea
     id: question
@@ -38,7 +38,7 @@ body:
     id: terms
     attributes:
       label: 📜 Code of Conduct
-      description: By submitting this issue, you agree to follow our [`Code of Conduct`](https://github.com/DariuszPorowski/ghaction-dump-contexts/blob/main/.github/CODE_OF_CONDUCT.md)
+      description: By submitting this issue, you agree to follow our [`Code of Conduct`](https://github.com/raven-actions/dump-contexts/blob/main/.github/CODE_OF_CONDUCT.md)
       options:
         - label: I agree to follow this project's Code of Conduct.
           required: true

.github/PULL_REQUEST_TEMPLATE.md

@@ -11,7 +11,7 @@ Fixes: #
 
 <!-- Mark with an `x` all the checkboxes that apply (like `[x]`) -->
 
-- [ ] 📚 Examples / docs / tutorials / dependencies update
+- [ ] 📚 Examples / docs / tutorials
 - [ ] 🐛 Bug fix (non-breaking change which fixes an issue)
 - [ ] 🥂 Improvement (non-breaking change which improves an existing feature)
 - [ ] 🚀 New feature (non-breaking change which adds functionality)
@@ -23,5 +23,5 @@ Fixes: #
 
 <!-- Mark with an `x` all the checkboxes that apply (like `[x]`) -->
 
-- [ ] I've read the [`Code of Conduct`](https://github.com/DariuszPorowski/ghaction-dump-contexts/blob/main/.github/CODE_OF_CONDUCT.md) document.
-- [ ] I've read the [`Contributing`](https://github.com/DariuszPorowski/ghaction-dump-contexts/blob/main/.github/CONTRIBUTING.md) guide.
+- [ ] I've read the [`Code of Conduct`](https://github.com/raven-actions/dump-contexts/blob/main/.github/CODE_OF_CONDUCT.md)> document.
+- [ ] I've read the [`Contributing`](https://github.com/raven-actions/dump-contexts/blob/main/.github/CONTRIBUTING.md) guide.

.github/SECURITY.md

@@ -8,24 +8,26 @@
 
 ## 🚨 Reporting a Vulnerability
 
+> ⚠️ **Please do not report security vulnerabilities through public GitHub issues.**
+
 If you believe you have found a security vulnerability in the project, please do not hesitate to report it to us. We take all security issues seriously and will do our best to address them promptly.
 
-To report a security vulnerability, please send a [Twitter message](https://twitter.com/DariuszPorowski) describing the vulnerability. In addition, please include any relevant information that could help us reproduce the issue, such as steps to reproduce the vulnerability, the affected versions of the software, and any other relevant details.
+To report a security vulnerability, please send a [LinkedIn message](https://www.linkedin.com/in/DariuszPorowski) describing the vulnerability. In addition, please include any relevant information that could help us reproduce the issue, such as steps to reproduce the vulnerability, the affected versions of the software, and any other relevant details.
 
-We will acknowledge receipt of your report within 2 business days and work with you to verify the vulnerability and develop a fix. We may also ask you for additional information or clarifications as needed.
+We will acknowledge receipt of your report within two business days and work with you to verify the vulnerability and develop a fix. We may also ask you for additional information or clarifications as needed.
 
 ## ⏳ Response Time
 
-We strive to address security issues as quickly as possible. Our response time depends on the severity of the issue, but we will do our best to provide a fix or a workaround within one week of receiving a vulnerability report. In some cases, it may take longer to address a security issue, but we will keep you updated on our progress.
+We strive to address security issues as quickly as possible. Our response time depends on the severity of the issue, but we will do our best to provide a fix or a workaround within one week of receiving a vulnerability report. Sometimes, it may take longer to address a security issue, but we will keep you updated on our progress.
 
 ## 👁️ Disclosure Policy
 
 We will disclose security vulnerabilities in our project as soon as we have verified them and developed a fix or a workaround. We will notify users of the vulnerability via our GitHub repository and other appropriate channels.
 
 ## 📜 Code of Conduct
 
-All participants in our project are expected to adhere to our [`Code of Conduct`](https://github.com/DariuszPorowski/ghaction-dump-contexts/blob/main/.github/CODE_OF_CONDUCT.md). Furthermore, we expect everyone to treat each other respectfully and contribute to a positive and inclusive community.
+All participants in our project are expected to adhere to our [`Code of Conduct`](https://github.com/raven-actions/dump-contexts/blob/main/.github/CODE_OF_CONDUCT.md). Furthermore, we expect everyone to treat each other respectfully and contribute to a positive and inclusive community.
 
 ## ✉️ Contact
 
-If you have any questions or concerns about our security policy, don't hesitate to contact us using [Twitter message](https://twitter.com/DariuszPorowski).
+If you have any questions or concerns about our security policy, don't hesitate to contact me using [LinkedIn message](https://www.linkedin.com/in/DariuszPorowski).

.github/dependabot.yml

@@ -1,11 +1,11 @@
 # Please see the documentation for all configuration options:
 # https://docs.github.com/github/administering-a-repository/configuration-options-for-dependency-updates
-
+---
 version: 2
 updates:
   - package-ecosystem: github-actions
     directory: /
     schedule:
       interval: daily
     commit-message:
-      prefix: "[github-actions] :arrow_up: "
+      prefix: "[github-actions] ⬆️ "