Merge branch 'master' into standalone

Author: vedansh-5

.github/ISSUE_TEMPLATE.md

@@ -1,15 +1,34 @@
-**Actual Behaviour**
+---
+name: Bug Report / Feature Request
+about: Report a bug or request a new feature
+title: '[Bug/Feature]: <short description>'
+labels: ['needs triage']
+assignees: ''
+---
 
-Please state here what is currently happening.
+### 🔍 Actual Behaviour
 
-**Expected Behaviour**
+What is currently happening?
 
-State here what the feature should enable the user to do.
+### ✅ Expected Behaviour
 
-**Screenshots of the issue**
+What should ideally happen?
 
-Where-ever possible attach a screenshot of the issue.
+### 📸 Screenshots
 
-**Would you like to work on the issue?**
+If applicable, add screenshots to help explain the issue.
 
-Please let us know if you can work on it or the issue should be assigned to someone else.
+### 🧪 Steps to Reproduce (for bugs)
+
+1. Go to '...'
+2. Click on '...'
+3. Scroll down to '...'
+4. See the error
+
+### 💡 Possible Solution
+
+(Optional) Suggest a fix or reason for the bug.
+
+### 🙋‍♂️ Would You Like to Work on It?
+
+Yes / No

.github/PULL_REQUEST_TEMPLATE.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_

README.md

@@ -2,14 +2,13 @@
 
 **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  
+- Fetches your GitHub PRs, Issues, and reviewed PRs
+- Auto-generates scrum updates
+- Supports Google Groups, Gmail, Yahoo, and Outlook compose windows
 
 ## How to install
 
@@ -21,16 +20,19 @@
 6. Fill in your settings in the popup (GitHub username, date range, etc.)
 
 ## Usage
-### For Google Groups:  
+
+### 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.  
+
+- 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
+- The extension will prefill scrum content for you to edit
 
 ### New Features
 1. **Standalone Popup Interface**
@@ -51,14 +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: