all files related to github actions completed

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -52,4 +52,4 @@ body:
         - label: "I'm a GSSOC'24 contributor"
           required: False
         - label: "I have starred the repository"
-          required: true
+          required: true

.github/ISSUE_TEMPLATE/documentation_update.yml

@@ -57,4 +57,4 @@ body:
         - label: "I'm a GSSOC'24 contributor"
           required: false
         - label: "I have starred the repository"
-          required: true
+          required: true

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -60,4 +60,4 @@ body:
         - label: "I'm a GSSOC'24 contributor"
           required: false
         - label: "I have starred the repository"
-          required: true
+          required: true

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,31 @@
+# Pull Request
+
+### Title
+<!-- Provide a clear and concise title for the pull request -->
+
+### Description
+<!-- Brief summary of the changes made and the purpose of the PR -->
+
+### Related Issues
+<!-- Mention any related issue numbers (e.g., "Fixes #123") -->
+
+### Changes Made
+<!-- List of changes made in the PR (e.g., new features, bug fixes, improvements) -->
+
+### Checklist 
+<!-- 
+This is how you check the check boxes where ever there is "[ ]" change it to [x]
+- [ ] Unchecked box
+- [x] Checked box
+ -->
+- [ ] I have tested the changes locally
+- [ ] Documentation has been updated (if necessary)
+- [ ] Changes are backward-compatible
+
+### Screenshots (if applicable)
+<!-- Add any relevant screenshots to illustrate the changes -->
+
+### Additional Notes
+<!-- Any additional information that might be helpful for the reviewer -->
+
+Footer

.github/workflows/autocomment-iss-close.yml

@@ -0,0 +1,29 @@
+name: Comment on Issue Close
+
+on:
+  issues:
+    types: [closed]
+
+jobs:
+  greet-on-close:
+    runs-on: ubuntu-latest
+    permissions:
+      issues: write
+    steps:
+      - name: Greet User
+        uses: actions/github-script@v5
+        with:
+          github-token: ${{ secrets.GITHUB_TOKEN }}
+          script: |
+            const issue = context.payload.issue;
+            const issueCreator = issue.user.login;
+            const issueNumber = issue.number;
+
+            const greetingMessage = `Hello @${issueCreator}! Your issue #${issueNumber} has been closed. Thank you for your contribution!`;
+
+            github.rest.issues.createComment({
+              owner: context.repo.owner,
+              repo: context.repo.repo,
+              issue_number: issueNumber,
+              body: greetingMessage
+            });

.github/workflows/autocomment-issue.yml

@@ -0,0 +1,36 @@
+name: Auto Comment on Issue
+
+on:
+  issues:
+    types: [opened]
+
+permissions:
+  issues: write
+
+jobs:
+  comment:
+    runs-on: ubuntu-latest
+    permissions:
+      issues: write
+    steps:
+      - name: Add Comment to Issue
+        run: |
+          COMMENT=$(cat <<EOF
+          {
+            "body": "Thank you for creating this issue! 🎉 We'll look into it as soon as possible. In the meantime, please make sure to provide all the necessary details and context. If you have any questions or additional information, feel free to add them here. Your contributions are highly appreciated! 😊\n\nYou can also check our [CONTRIBUTING.md](https://github.com/VaibhavArora314/StyleShare/blob/main/CONTRIBUTING.md) for guidelines on contributing to this project."
+          }
+          EOF
+          )
+          RESPONSE=$(curl -s -o response.json -w "%{http_code}" \
+            -X POST \
+            -H "Authorization: token ${{ secrets.GITHUB_TOKEN }}" \
+            -H "Accept: application/vnd.github.v3+json" \
+            https://api.github.com/repos/${{ github.repository }}/issues/${{ github.event.issue.number }}/comments \
+            -d "$COMMENT")
+          cat response.json
+          if [ "$RESPONSE" -ne 201 ]; then
+            echo "Failed to add comment"
+            exit 1
+          fi
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

.github/workflows/autocomment-pr-merge.yml

@@ -0,0 +1,37 @@
+name: Auto Comment on PR Merge
+
+on:
+  pull_request_target:
+    types: [closed]
+
+permissions:
+  issues: write
+  pull-requests: write
+
+jobs:
+  comment:
+    if: github.event.pull_request.merged == true
+    runs-on: ubuntu-latest
+
+    steps:
+     - name: Add Comment to Merged PR
+       run: |
+        COMMENT=$(cat <<EOF
+        {
+          "body": "🎉 Your pull request has been successfully merged! 🎉 Thank you for your valuable contribution to our project. Your efforts are greatly appreciated. Feel free to reach out if you have any more contributions or if there's anything else we can assist you with. Keep up the fantastic work! 🚀"
+        }
+        EOF
+        )
+        RESPONSE=$(curl -s -o response.json -w "%{http_code}" \
+          -X POST \
+          -H "Authorization: token ${{ secrets.GITHUB_TOKEN }}" \
+          -H "Accept: application/vnd.github.v3+json" \
+          https://api.github.com/repos/${{ github.repository }}/issues/${{ github.event.pull_request.number }}/comments \
+          -d "$COMMENT")
+        cat response.json
+        if [ "$RESPONSE" -ne 201 ]; then
+          echo "Failed to add comment"
+          exit 1
+        fi
+       env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

.github/workflows/autocomment-pr-raise.yml

@@ -0,0 +1,37 @@
+name: Auto Comment on PR
+
+on:
+  pull_request_target:
+    types: [opened]
+
+permissions:
+  issues: write
+  pull-requests: write
+
+jobs:
+  comment:
+    runs-on: ubuntu-latest
+    permissions:
+      pull-requests: write
+    steps:
+    - name: Add Comment to Pull Request
+      run: |
+        COMMENT=$(cat <<EOF
+        {
+          "body": "Thank you for submitting your pull request! 🙌 We'll review it as soon as possible. In the meantime, please ensure that your changes align with our [CONTRIBUTING.md](https://github.com/VaibhavArora314/StyleShare/blob/main/CONTRIBUTING.md). If there are any specific instructions or feedback regarding your PR, we'll provide them here. Thanks again for your contribution! 😊"
+        }
+        EOF
+        )
+        RESPONSE=$(curl -s -o response.json -w "%{http_code}" \
+          -X POST \
+          -H "Authorization: token ${{ secrets.GITHUB_TOKEN }}" \
+          -H "Accept: application/vnd.github.v3+json" \
+          https://api.github.com/repos/${{ github.repository }}/issues/${{ github.event.pull_request.number }}/comments \
+          -d "$COMMENT")
+        cat response.json
+        if [ "$RESPONSE" -ne 201 ]; then
+          echo "Failed to add comment"
+          exit 1
+        fi
+      env:
+        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

.github/workflows/close-old-issue.yml

@@ -0,0 +1,37 @@
+name: Close Old Issues
+on:
+  schedule:
+    - cron: "0 0 * * *"
+
+jobs:
+  close-issues:
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout Repository
+        uses: actions/checkout@v4
+
+      - name: Close Old Issues
+        run: |
+          open_issues=$(curl -s -H "Authorization: token ${{ secrets.GITHUB_TOKEN }}" \
+            "https://api.github.com/repos/${{ github.repository }}/issues?state=open" \
+            | jq -r '.[] | .number')
+          for issue in $open_issues; do
+            # Get the last updated timestamp of the issue
+            last_updated=$(curl -s -H "Authorization: token ${{ secrets.GITHUB_TOKEN }}" \
+              "https://api.github.com/repos/${{ github.repository }}/issues/$issue" \
+              | jq -r '.updated_at')
+            days_since_update=$(( ( $(date +%s) - $(date -d "$last_updated" +%s) ) / 86400 ))
+            if [ $days_since_update -gt 30 ]; then
+              curl -s -X PATCH -H "Authorization: token ${{ secrets.GITHUB_TOKEN }}" \
+                -H "Accept: application/vnd.github.v3+json" \
+                -d '{"state":"closed"}' \
+                "https://api.github.com/repos/${{ github.repository }}/issues/$issue"
+              
+              # Add a comment explaining when the issue will be closed
+              curl -s -X POST -H "Authorization: token ${{ secrets.GITHUB_TOKEN }}" \
+                -H "Accept: application/vnd.github.v3+json" \
+                -d '{"body":"This issue has been automatically closed because it has been inactive for more than 30 days. If you believe this is still relevant, feel free to reopen it or create a new one. Thank you!"}' \
+                "https://api.github.com/repos/${{ github.repository }}/issues/$issue/comments"
+            fi
+          done

.github/workflows/close-old-pr.yml

@@ -0,0 +1,34 @@
+name: Close Stale PRs
+
+on:
+  schedule:
+    - cron: '0 0 * * *' # Runs daily at midnight
+  pull_request:
+    types:
+      - opened
+      - reopened
+      - synchronize
+
+permissions:
+  pull-requests: write
+  issues: write
+
+jobs:
+  close_stale_prs:
+    runs-on: ubuntu-latest
+    permissions:
+      pull-requests: write
+
+    steps:
+    - uses: actions/stale@v7
+      with:
+        repo-token: ${{ secrets.GITHUB_TOKEN }}
+        stale-pr-message: 'This PR has been automatically closed due to inactivity from the owner for 15 days.'
+        days-before-pr-stale: 15
+        days-before-pr-close: 0
+        exempt-pr-author: false
+        exempt-pr-labels: ''
+        only-labels: ''
+        operations-per-run: 30
+        remove-stale-when-updated: true
+        debug-only: false

CODE_OF_CONDUCT.md

@@ -0,0 +1,50 @@
+# Style Share Project Code of Conduct
+
+Style Share is dedicated to providing a positive, respectful, and inclusive environment for all contributors and users. We have established this Code of Conduct to outline our expectations for behavior within our community. This code applies to all interactions within the project, including discussions, contributions, and events.
+
+## Our Values
+
+- **Respect**: Treat all individuals with kindness, empathy, and consideration.
+- **Inclusivity**: Embrace diversity of perspectives and backgrounds.
+- **Collaboration**: Foster a spirit of cooperation and teamwork.
+- **Open-mindedness**: Be open to new ideas, constructive feedback, and differing viewpoints.
+
+## 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.
+
+## Expected Behavior
+
+When participating in the Style Share community, we expect all contributors and users to:
+
+- Be respectful and considerate towards others.
+- Use welcoming and inclusive language.
+- Listen actively and be open to differing opinions.
+- Show empathy towards others' experiences and abilities.
+- Constructively critique ideas and avoid personal attacks.
+- Strive towards a harmonious and collaborative environment.
+
+## Unacceptable Behavior
+
+Unacceptable behaviors include, but are not limited to:
+
+- Harassment, discrimination, or offensive language.
+- Intimidation, trolling, or deliberate antagonism.
+- Personal insults, derogatory remarks, or attacks.
+- Any form of unwelcome or inappropriate conduct.
+- Disrespect towards differing viewpoints or experiences.
+- Engaging in behavior that disrupts the positive atmosphere of the community.
+
+## Reporting Guidelines
+
+If you experience or witness any behavior that violates this Code of Conduct, please report it to the project maintainers immediately. All complaints will be reviewed and investigated promptly and fairly.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may result in corrective actions, including warnings, temporary bans, or permanent bans, as deemed appropriate by the project maintainers. 
+
+By participating in Style Share, you are expected to uphold this Code of Conduct. We aim to cultivate a community where everyone feels safe and valued.