Merge branch 'ui2' of https://github.com/vedansh-5/scrum_helper into ui2

Author: vedansh-5

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,38 @@
+---  
+name: Bug Report  
+about: Report a bug or unexpected behavior  
+title: "[Bug] "  
+labels: bug  
+assignees: ''
+  
+---  
+
+## Bug Description
+A clear and concise description of what the bug is.
+
+### Steps 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.
+
+### Actual Behavior
+A clear and concise description of what actually happened.
+
+### Screenshots
+If applicable, add screenshots to help explain your problem.
+
+### Additional Context
+Add any other context about the problem here.
+  
+---  
+
+## Contribution Checklist
+- [ ] I have searched existing issues to ensure this bug hasn't been reported
+- [ ] I have provided clear reproduction steps
+- [ ] I have included relevant environment details
+- [ ] I have described both expected and actual behavior  

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,33 @@
+---
+name: Feature or Enhancement Request
+about: Suggest a new feature or improvement to existing functionality
+title: '[Enhancement]: <short description>'
+labels: ['enhancement']
+assignees: ''
+---
+
+##  Enhancement Summary
+A clear and concise description of the enhancement or feature you'd like to see.
+
+###  Motivation
+Why is this feature needed? What problem does it solve or what value does it add?
+
+###  Proposed Solution
+Describe your idea or how you would like it to work.
+
+###  Alternatives Considered
+Have you thought of any other ways to solve the problem?
+
+###  Screenshots / Mockups
+If applicable, add visuals or examples of how this could look/work.
+
+###  Additional Context
+Any other relevant information or use cases.
+
+---
+
+##  Contribution Checklist
+- [ ] I have checked existing enhancement requests
+- [ ] I have clearly described the proposed change
+- [ ] I have explained the motivation and context
+- [ ] I am willing to help implement this feature (optional)

.github/ISSUE_TEMPLATE/feature_request.md

@@ -1,5 +1,31 @@
-Fixes issue #[Add issue number here. If you do not solve the issue entirely, please change the message e.g. "First steps for issues #IssueNumber]
+### 📌 Fixes
 
-Changes: [Add here what changes were made in this issue and if possible provide links.]
+Fixes #<issue-number> (Use "Fixes", "Closes", or "Resolves" for automatic closing)
 
-Screenshots for the change:
+---
+
+### 📝 Summary of Changes
+
+- Short description of what was changed
+- Include links to related issues/discussions if any
+
+---
+
+### 📸 Screenshots / Demo (if UI-related)
+
+_Add screenshots, video, or link to deployed preview if applicable_
+
+---
+
+### ✅ Checklist
+
+- [ ] I’ve tested my changes locally
+- [ ] I’ve added tests (if applicable)
+- [ ] I’ve updated documentation (if applicable)
+- [ ] My code follows the project’s code style guidelines
+
+---
+
+### 👀 Reviewer Notes
+
+_Add any special notes for the reviewer here_

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,31 @@
+name-template: 'v$RESOLVED_VERSION 🌈'
+tag-template: 'v$RESOLVED_VERSION'
+categories:
+  - title: '🚀 Features'
+    labels:
+      - 'feature'
+      - 'enhancement'
+  - title: '🐛 Bug Fixes'
+    labels:
+      - 'fix'
+      - 'bugfix'
+      - 'bug'
+  - title: '🧰 Maintenance'
+    labels: 'chore'
+change-template: '- $TITLE @$AUTHOR (#$NUMBER)'
+change-title-escapes: '\<*_&' # You can add # and @ to disable mentions, and add ` to disable code blocks.
+version-resolver:
+  major:
+    labels:
+      - 'major'
+  minor:
+    labels:
+      - 'minor'
+  patch:
+    labels:
+      - 'patch'
+  default: patch
+template: |
+  ## Changes
+
+  $CHANGES

.github/release-drafter.yml

@@ -0,0 +1,42 @@
+name: Release Drafter
+
+on:
+  push:
+    # branches to consider in the event; optional, defaults to all
+    branches:
+      - master
+
+  # pull_request event is required only for autolabeler
+  pull_request:
+    # Only following types are handled by the action, but one can default to all as well
+    types: [opened, reopened, synchronize]
+  # pull_request_target event is required for autolabeler to support PRs from forks
+  # pull_request_target:
+  #   types: [opened, reopened, synchronize]
+
+permissions:
+  contents: read
+
+jobs:
+  update_release_draft:
+    permissions:
+      # write permission is required to create a github release
+      contents: write
+      # write permission is required for autolabeler
+      # otherwise, read permission is required at least
+      pull-requests: write
+    runs-on: ubuntu-latest
+    steps:
+      # (Optional) GitHub Enterprise requires GHE_HOST variable set
+      #- name: Set GHE_HOST
+      #  run: |
+      #    echo "GHE_HOST=${GITHUB_SERVER_URL##https:\/\/}" >> $GITHUB_ENV
+
+      # Drafts your next Release notes as Pull Requests are merged into "master"
+      - uses: release-drafter/release-drafter@v6.1.0
+        # (Optional) specify config name to use, relative to .github/. Default: release-drafter.yml
+        # with:
+        #   config-name: my-config.yml
+        #   disable-autolabeler: true
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

.github/workflows/release-drafter.yml

@@ -1,23 +1,50 @@
 # SCRUM Helper
 
-This chrome extension helps you to write scrums in google groups for FOSSASIA related projects. You need to add your github username, dates, and other options. It fetches your PRs, Issues, and the PRs you reviewed from Github API, and prefills the SCRUM. You can edit the scrum further to meet your needs.
+**SCRUM Helper** is a Chrome extension designed to simplify writing scrums in Google Groups for FOSSASIA projects. By adding your GitHub username, date range, and other options, it automatically fetches your PRs, Issues, and reviewed PRs via the GitHub API and pre-fills the scrum. You can then edit the scrum to fit your needs.
 
 ![SCRUMLOGO](docs/images/scrumhelper-png.png)
 
+## Features
+
+- Fetches your GitHub PRs, Issues, and reviewed PRs
+- Auto-generates scrum updates
+- Supports Google Groups, Gmail, Yahoo, and Outlook compose windows
+
 ## How to install
 
 1. Clone this repository to your local machine.
 2. Go to `chrome://extensions` on your chrome browser.
-3. Turn on developer mode if not already on.
-4. Load unpacked extension from `src` folder.
-5. Click on the Scrum Helper icon you see on your browser toolbar.
-6. Fill in the settings in the popup.
-7. **For Google Groups:**  
-   - Open https://groups.google.com/forum/#!newtopic/<groupname> and start a New Conversation.  
-8. Refresh the page to apply the new settings.  
-9. **For Gmail, Yahoo, and Outlook:**  
-   - Open the Compose window.  
-   - Follow Step 8 to ensure the settings take effect.  
+3. Enable Developer Mode (toggle in the top-right) if not already.
+4. Click Load unpacked and select the `src` folder inside the cloned repo
+5. Click the Scrum Helper icon on your browser toolbar
+6. Fill in your settings in the popup (GitHub username, date range, etc.)
+
+## Usage
+
+### For Google Groups:
+
+- Open Google Groups New Topic
+- Start a New Conversation
+- Refresh the page to apply the Scrum Helper settings
+- Use the pre-filled scrum and edit as needed
+
+### For Gmail, Yahoo, and Outlook:
+
+- Open the Compose window.
+- Ensure the Scrum Helper settings are applied (follow step 6 above)
+- The extension will prefill scrum content for you to edit
+
+### New Features
+1. **Standalone Popup Interface**
+   - Generate reports directly from the extension popup
+   - Live preview of the report before sending
+   - Rich text formatting with clickable links
+   - Copy report to clipboard with proper formatting
+
+### Usage Standalone
+- Click on `GENERATE` button to generate the scrum preview.
+- Edit it in the window.
+- Copy the rich HTML using the `COPY` button.
 
 ## Setting up the code locally
 
@@ -26,12 +53,52 @@ $ git clone https://github.com/fossasia/scrum_helper/
 $ cd scrum_helper
 $ npm install
 ```
+
 ## Screenshots
+
 ![SCRUM](/docs/images/scrum.png)
 
 ![POPUP](/docs/images/popup.png)
 
+![STANDALONE](docs/images/standalone.png)
+
+## Using Scrum Helper with Your Own GitHub Organization
+
+Scrum Helper is not limited to the [FOSSASIA](https://github.com/fossasia) organization. You can easily configure it to fetch and generate SCRUM reports for your own GitHub organization or repositories.
+
+### Steps to Set It Up for Your Organization
+
+1. **Install the Extension**
+
+- Load it into your browser through [Chrome Extension Developer Mode](https://developer.chrome.com/docs/extensions/mv3/getstarted/).
+
+2. **Update the Organization**
+
+   - Currently, the extension uses `org:fossasia` to fetch GitHub issues and PRs.
+   - To make it work with your GitHub organization:
+     - Open `scrumHelper.js` (or wherever the GitHub API URLs are defined).
+     - Replace:
+       ```js
+       +org:fossasia+
+       ```
+       with:
+       ```js
+       +org:your-org-name+
+       ```
+       **Example**
+       ![Code Snippet ](<Screenshot 2025-05-30 205822.png>)
+
+3. **Build the Extension**
+
+   - Save your changes.
+   - Rebuild or reload the extension in your browser (`chrome://extensions` → Refresh your extension).
+
+4. **Get Customized SCRUM Reports**
+   - The reports will now be generated using contributions from your organization.
+
+
 ## About contributing
+
 - Follow the Issues and PRs templates as far as possible.
 - If you want to make a PR, please mention in the corresponding issue that you are working on it.
 - Before making a PR, ensure your code is properly formatted and linted: