Merge branch 'main' into master

.github/ISSUE_TEMPLATE/01-bug.yml

@@ -0,0 +1,57 @@
+name: Bug Report
+description: File a bug report.
+title: "[BUG]: "
+labels: ["bug"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to fill out this bug report!
+  - type: textarea
+    id: what-happened
+    attributes:
+      label: What happened?
+      description: Also tell us, what did you expect to happen?
+      placeholder: Tell us what you see!
+      value: |
+        # Description  
+        
+        # Steps to Reproduce  
+        -
+        -
+        
+        # Expected Behavior  
+        
+        # Actual Behavior  
+        
+        # Screenshots
+
+    validations:
+      required: true
+  - type: dropdown
+    id: browsers
+    attributes:
+      label: What browsers are you seeing the problem on?
+      multiple: true
+      options:
+        - Firefox
+        - Chrome
+        - Safari
+        - Microsoft Edge
+  - type: dropdown
+    id: screensizes
+    attributes:
+      label: What screen size are you seeing the problem on?
+      multiple: true
+      options:
+        - Desktop
+        - Tablet
+        - Mobile
+  - type: checkboxes
+    id: terms
+    attributes:
+      label: Code of Conduct
+      description: By submitting this issue, you agree to follow our [Code of Conduct](https://github.com/OkenHaha/react-blog/blob/main/CODE_OF_CONDUCT.md). 
+      options:
+        - label: I agree to follow this project's Code of Conduct
+          required: true

.github/ISSUE_TEMPLATE/02-feature.yml

@@ -0,0 +1,36 @@
+name: Feature Request
+description: Suggest an idea for this project.
+title: "[FEAT]: "
+labels: ["enhancement"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to suggest a New Feature!
+  - type: textarea
+    id: new-feature
+    attributes:
+      label: What is the Feature/Idea?
+      description: "A new feature!"
+      value: |
+        ## Is your feature request related to a problem/idea? Please describe.
+        A clear and concise description of what the problem/idea is.
+
+        ## Describe the solution you'd like
+        A clear and concise description of what you want to happen.
+
+        ## 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 or screenshots about the feature request here.
+    validations:
+      required: true
+  - type: checkboxes
+    id: terms
+    attributes:
+      label: Code of Conduct
+      description: By submitting this issue, you agree to follow our [Code of Conduct](https://github.com/OkenHaha/react-blog/blob/main/CODE_OF_CONDUCT.md).
+      options:
+        - label: I agree to follow this project's Code of Conduct
+          required: true

.github/ISSUE_TEMPLATE/03-documentation.yml

@@ -0,0 +1,42 @@
+name: Documentation
+description: Suggest updates, fixes, or additions to the documentation.
+title: "[DOCS]: "
+labels: ["documentation"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to update the Documentation!
+  - type: textarea
+    id: docs
+    attributes:
+      label: What are the changes you propose?
+      description: "A documentation upgrade!"
+      value: |
+        **Describe the change that is needed**
+        A clear and concise description of what needs to be updated, fixed, or added in the documentation.
+
+        **Location of the documentation**
+        Provide links or specific sections/pages where the changes are required (e.g., README.md, docs/setup-guide.md).
+
+        **Reason for the change**
+        Explain why this change is necessary. For example:
+        - Is the documentation incorrect?
+        - Is there missing information?
+        - Is the existing documentation unclear or outdated?
+
+        **Suggested changes**
+        If possible, provide a clear outline or snippet of the suggested changes.
+
+        **Additional context**
+        Add any other context, screenshots, or examples to support the documentation change request.
+    validations:
+      required: true
+  - type: checkboxes
+    id: terms
+    attributes:
+      label: Code of Conduct
+      description: By submitting this issue, you agree to follow our [Code of Conduct](https://github.com/OkenHaha/react-blog/blob/main/CODE_OF_CONDUCT.md).
+      options:
+        - label: I agree to follow this project's Code of Conduct
+          required: true

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,8 @@
+blank_issues_enabled: false
+contact_links:
+  - name: General Question
+    url: https://github.com/OkenHaha/react-blog/discussions
+    about: If you have a general question or need help, start a discussion here.
+  - name: Report Security Vulnerability
+    url: mailto:[email protected]
+    about: If you found a security issue, please report it confidentially using this link.

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,14 @@
+## 📝 Description
+Describe the changes you have done in this pull request.
+
+## 🔗 Related Issues
+- Closes #<issue_number>
+- Related to #<issue_number> (optional)
+
+## 📸 Screenshots / 📹 Videos
+Attach screenshots or screen recordings showcasing the changes, if applicable.
+
+## ✅ Checklist
+- [ ] I have read and followed the [Contributing Guidelines](https://github.com/OkenHaha/react-blog/blob/main/CONTRIBUTING.md).
+- [ ] I have tested my changes by running it, and works as expected.
+- [ ] I have tested these changes in at least Chrome and Firefox (other browsers if applicable).

.github/workflows/auto-comment.yml

@@ -0,0 +1,75 @@
+name: Automate Issue and PR Responses
+
+on:
+ issues:
+ types:
+ - opened
+ - closed
+ pull_request:
+ types:
+ - opened
+ - closed
+
+jobs:
+ respond-to-events:
+ runs-on: ubuntu-latest
+
+ steps:
+ - name: Checkout repository
+ uses: actions/checkout@v3
+
+ # Respond to new issues
+ - name: Respond to new issues
+ if: ${{ github.event_name == 'issues' && github.event.action == 'opened' }}
+ run: |
+ echo "Hey @${{ github.actor }}, Welcome to 💖react-blog! 🎊" > comment.txt
+ echo "Thanks for opening an issue! 🙌 Please wait for the issue to be assigned." >> comment.txt
+ echo "Happy Coding!! ✨" >> comment.txt
+ env:
+ GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+ uses: peter-evans/create-or-update-comment@v3
+ with:
+ issue-number: ${{ github.event.issue.number }}
+ body-path: comment.txt
+
+ # Respond to closed issues
+ - name: Respond to closed issues
+ if: ${{ github.event_name == 'issues' && github.event.action == 'closed' }}
+ run: |
+ echo "Hello @${{ github.event.issue.user.login }}! Your issue #${{ github.event.issue.number }} has been closed." > comment.txt
+ echo "Thank you for your contribution to 💖react-blog!!! 🙌" >> comment.txt
+ env:
+ GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+ uses: peter-evans/create-or-update-comment@v3
+ with:
+ issue-number: ${{ github.event.issue.number }}
+ body-path: comment.txt
+
+ # Respond to new PRs
+ - name: Respond to new PRs
+ if: ${{ github.event_name == 'pull_request' && github.event.action == 'opened' }}
+ run: |
+ echo "Hey @${{ github.actor }}, Welcome to 💖react-blog 🎊" > comment.txt
+ echo "Thanks for your contribution! Your effort makes this project better. Keep it up! 🙌" >> comment.txt
+ echo "Please wait for the PR to be reviewed." >> comment.txt
+ echo "Happy Coding!! ✨" >> comment.txt
+ env:
+ GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+ uses: peter-evans/create-or-update-comment@v3
+ with:
+ issue-number: ${{ github.event.pull_request.number }}
+ body-path: comment.txt
+
+ # Respond to merged PRs
+ - name: Respond to merged PRs
+ if: ${{ github.event_name == 'pull_request' && github.event.action == 'closed' && github.event.pull_request.merged }}
+ run: |
+ echo "@${{ github.event.pull_request.user.login }} Congrats, Your pull request has been successfully merged 🥳🎉" > comment.txt
+ echo "Thank you for your contribution to 💖react-blog!!" >> comment.txt
+ echo "Happy coding 🎊, Keep Contributing 🙌 !!!" >> comment.txt
+ env:
+ GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+ uses: peter-evans/create-or-update-comment@v3
+ with:
+ issue-number: ${{ github.event.pull_request.number }}
+ body-path: comment.txt

CODE_OF_CONDUCT.md

@@ -0,0 +1,67 @@
+# 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 [[email protected]](mailto:[email protected]). 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. 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. During this period, no public or private interaction with the community is allowed. 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.1, available at [https://www.contributor-covenant.org/version/2/1/code_of_conduct.html](https://www.contributor-covenant.org/version/2/1/code_of_conduct.html).
+
+For answers to common questions about this code of conduct, see the FAQ at [https://www.contributor-covenant.org/faq](https://www.contributor-covenant.org/faq). Translations are available at [https://www.contributor-covenant.org/translations](https://www.contributor-covenant.org/translations).