Skip to content

feat: add bloated devcontainer and remove project governance templates#52

Merged
AnkanSaha merged 1 commit intomainfrom
maintainer/ankan
Mar 15, 2026
Merged

feat: add bloated devcontainer and remove project governance templates#52
AnkanSaha merged 1 commit intomainfrom
maintainer/ankan

Conversation

@AnkanSaha
Copy link
Copy Markdown
Member

@AnkanSaha AnkanSaha commented Mar 15, 2026

Summary

This PR introduces a heavy-duty DevContainer configuration and inexplicably deletes all GitHub issue and pull request templates. It also bumps the version from v5.19 to v5.21.

Changes

  • Added .devcontainer/devcontainer.json with extreme resource requirements (GPU, 20GB disk).
  • Added postCreateCommand.sh that installs multiple AI CLIs and uses npm install --force across sub-directories.
  • Deleted .github/ISSUE_TEMPLATE/bug_report.md, feature_request.md, and pull_request_template.md.
  • Bumped VERSION to v5.21.

Verification

  • Devcontainer builds (pray for the RAM).
  • Global CLIs are accessible.
  • Templates are gone (unfortunately).

…js environment setup

chore: Remove outdated issue and pull request templates
chore: Update version to v5.21
@AnkanSaha AnkanSaha self-assigned this Mar 15, 2026
Copilot AI review requested due to automatic review settings March 15, 2026 13:03
@github-actions github-actions bot changed the title feat feat: add bloated devcontainer and remove project governance templates Mar 15, 2026
@github-actions
Copy link
Copy Markdown

🤖 Review Buddy - General Code Review

👥 Attention: @AnkanSaha @Copilot

Oye @AnkanSaha! Ye kya bawasir bana diye ho? PR title 'feat' likh ke chhodd diya, jaise hum antaryami hain ki samajh jayenge tumne kya kaand kiya hai. Devcontainer ke naam pe poora OS bhar diya hai aur Github templates aise delete kiye hain jaise ex ki photos.

Code Quality Score: 3/10. Bhai, thoda toh sharam karo, 'npm install --force' use kar rahe ho? Isse accha toh manual copy-paste hi kar lete. Aur ye GPU true kyun hai? Node.js mein kaunsa Ray Tracing kar rahe ho tum? Sudhar jao, varna agli baar terminal se bahar nikal ke maarunga.


Generated by Review Buddy | Tone: roast | Language: hinglish

@github-actions
Copy link
Copy Markdown

⚡ Review Buddy - Performance Analysis

👥 Attention: @AnkanSaha @Copilot

Arre bhai bhai bhai! Performance ke naam pe tumne toh maut ka nanga naach shuru kar diya hai.

  1. Resource Hunger: 20GB storage? 4GB RAM? GPU: true? Bhai Node.js project hai ya Cyberpunk 2077 chala rahe ho? Devcontainer ko itna heavy bana diya hai ki bechara Docker bhi ro raha hoga.

  2. The Layer Cake of Doom: postCreateCommand.sh mein tumne apt-get update toh kar diya, lekin cache clean karna bhool gaye? Container image ka size badhate hi jaoge kya?

  3. Dependency Hell: npm install --force teen-teen baar! Wo bhi recursive folders mein. Ek toh --force use karna paap hai, upar se tumne use loops ke bina manual likha hai. Agar 10 sub-projects hote toh kya 100 line likhte?

  4. AI CLI Bloat: Claude, Codex, Gemini, Copilot... Saare AI ek saath install kar diye. Memory footprint ka toh janaza nikal gaya hoga.

  5. Sequential Execution: Saare npm install ek ke baad ek ho rahe hain. Parallelization naam ki bhi koi cheez hoti hai duniya mein?

  6. Build Bottleneck: Har baar container banega, har baar ye poori duniya install karega. Productivity toh negative mein chali gayi hai.

  7. No Cleanup: apt-get ke baad /var/lib/apt/lists/* delete nahi kiya. Extra MBs bina kisi wajah ke.

  8. Neofetch Flex: Dev container mein neofetch kyun? Screenshot leke Twitter pe dalna hai kya? Ye resource waste hai boss.

  9. Node Source Redundancy: Bullseye image mein pehle se hi node hota hai aksar, lekin tumne phir se curl karke install kiya.

  10. Storage Bloat: 20GB requirement setup karke tumne cloud environments (like Codespaces) ka kharcha double karwa diya hai. Paisa kya ped pe ugta hai?

Recommendation: Use multi-stage builds, remove unnecessary global CLIs, and for the love of God, stop using --force.


Generated by Review Buddy | Tone: roast | Language: hinglish

@github-actions
Copy link
Copy Markdown

🔐 Review Buddy - Security Audit

👥 Attention: @AnkanSaha @Copilot

Security ka toh tumne mazaak bana diya hai.

  • Severity: Critical | Location: .devcontainer/devcontainer.json
    remoteUser: root? Bhai, chabi chor ko de di tumne. Container ke andar root banke kya ukhadna hai? Agar koi tool compromise hua, toh poora host system khatre mein hai.

  • Severity: High | Location: .devcontainer/postCreateCommand.sh
    curl ... | sudo -E bash... Bina script check kiye execute kar rahe ho? MITM attack ka naam suna hai kabhi?

  • Severity: Medium | Location: Global npm installs
    Char-char AI CLIs install kar rahe ho global permissions ke saath. Unke dependencies check kiye hain? Supply chain attack ke liye rasta saaf kar rahe ho.

  • Severity: Low | Location: apt-get update
    Bina version pinning ke package install kar rahe ho. Reproducible builds toh gaye tel lene, security patches ka bhi koi thikana nahi.

Remediation: Root user hatao, non-root user (node) use karo. Script piping band karo. OWASP Top 10 padho thoda.


Generated by Review Buddy | Tone: roast | Language: hinglish

@github-actions
Copy link
Copy Markdown

📊 Review Buddy - Code Quality & Maintainability Analysis

👥 Attention: @AnkanSaha @Copilot

🎯 Overall Benchmark: 25/100 (Poor)

Quality? Kaunsi quality? Yahan toh sirf chaos hai.

  1. SOLID Principles ka Qatal: Scripts mein koi structure nahi hai. Hardcoded paths (./Document, ./GUI) use kar rahe ho. Agar folder rename hua toh tumhari script collapse kar jayegi.

  2. DRY (Do Repeat Yourself): npm install --force && cd .. baar baar repeat ho raha hai. Function banana sikho, bhai.

  3. Process Destruction: Tumne bug_report.md, feature_request.md, aur pull_request_template.md delete kar diye. Team collaboration kaise hogi? Dream mein? Ye toh regression hai.

  4. Naming Conventions: Version bump v5.19 se seedha v5.21? Beech mein v5.20 kahan gaya? Tumhari ginti weak hai ya logic?

  5. Error Handling: postCreateCommand.sh mein agar ek bhi npm install fail hua, toh script aage badhti rahegi (unlikely due to && but still). Aur set -e kahan hai?

  6. Technical Debt: --force use karna technical debt nahi, technical bankruptcy hai. Dependencies resolve nahi ho rahi toh package.json theek karo, force mat karo.

  7. Documentation: Template delete kar diye aur koi nayi documentation di nahi. Great job, Sherlock!

  8. Bloated Extensions: VS Code mein itne extensions bhar diye hain ki editor khulne mein 2 saal lagayega. 'code-runner' aur 'thunder-client' dono? Choice toh rakho thodi.

  9. Indentation/Formatting: Shell script mein indentation ke naam pe khichdi pakayi hai.

  10. Missing Shebang Best Practices: #!/bin/bash toh theek hai, par set -euo pipefail use karte toh thodi izzat bach jati.

Refactoring suggestion: Use a loop for directory traversal and installation. Restore the deleted templates. Fix the user permissions.


Generated by Review Buddy | Tone: roast | Language: hinglish

@github-actions
Copy link
Copy Markdown

💡 Review Buddy - Best Practices & Alternative Suggestions

👥 Attention: @AnkanSaha @Copilot

Bhai, ye dekh aur seekh:

Current Bawasir:

cd ./Document && npm i --force && cd ..
cd ./GUI && npm i --force && cd ..

Better Alternative:

# Use a loop and avoid --force if possible
for dir in . ./Document ./GUI; do
  if [ -d "$dir" ]; then
    echo "Installing dependencies in $dir..."
    (cd "$dir" && npm install)
  fi
done

Why: Readability badhti hai aur code DRY rehta hai.

Current Risk:

"remoteUser": "root"

Better Alternative:

"remoteUser": "node"

Why: Least privilege principle, beta. Security 101.

Template Deletion:
Why did you delete the GitHub templates? Keep them to maintain project standards. Deleting them is NOT a feature.


Generated by Review Buddy | Tone: roast | Language: hinglish

@github-actions github-actions bot added the enhancement New feature or request label Mar 15, 2026
@github-actions
Copy link
Copy Markdown

🚫 Review Buddy - Final Recommendation

👥 Attention: @AnkanSaha @Copilot

Recommendation: REJECT

Arre bhai bhai bhai! Ye PR toh reject karna padega!

Reasoning:

  • The use of 'npm install --force' is unacceptable and hides dependency conflicts.
  • Removing GitHub issue and PR templates is a major regression in project management.
  • The devcontainer resource requirements are extremely high and unjustified (GPU for Node.js).
  • Running the container as 'root' is a significant security risk.
  • The version bump skips v5.20 without explanation.
  • PR title is non-descriptive and violates conventional commits.

📋 Review Checklist for Reviewers:

  • Code changes align with the PR description
  • No security vulnerabilities introduced
  • Performance considerations addressed
  • Code follows project conventions
  • Tests are adequate (if applicable)
  • Documentation updated (if needed)

🎯 Next Steps:

🚫 Critical issues hai - is PR ko reject karo aur major fixes ke baad dobara submit karo.

Generated by Review Buddy | Tone: roast | Language: hinglish

@AnkanSaha AnkanSaha merged commit 1e0f9a3 into main Mar 15, 2026
5 checks passed
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the repository version and introduces a VS Code Dev Container setup, while also removing GitHub PR/issue templates.

Changes:

  • Bump VERSION from v5.19 to v5.21.
  • Remove .github/pull_request_template.md and the issue templates for bugs/features.
  • Add a .devcontainer/ configuration and a post-create provisioning script.

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 8 comments.

Show a summary per file
File Description
VERSION Version bump to v5.21.
.github/pull_request_template.md Removes the PR template.
.github/ISSUE_TEMPLATE/feature_request.md Removes the feature request template.
.github/ISSUE_TEMPLATE/bug_report.md Removes the bug report template.
.devcontainer/devcontainer.json Adds a Dev Container configuration (currently missing a container definition).
.devcontainer/postCreateCommand.sh Adds provisioning steps for the devcontainer (currently references non-existent paths and has reproducibility/safety concerns).

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

"name": "Node.js & TypeScript",
"hostRequirements": {
"cpus": 2, // 2 CPUs are required for the universal image
"gpu": true, // GPU is required for the universal image
"forwardPorts": [
27018
],
"postCreateCommand": "./.devcontainer/postCreateCommand.sh",
Comment on lines +13 to +17
# Install Dependencies for the AxioDB Documentation
cd ./Document && npm i --force && cd .. # Install & build dependencies for AxioDB Documentation

# Install Dependencies for the AxioDB GUI
cd ./GUI && npm i --force && cd .. # Install & build dependencies for AxioDB GUI
Comment on lines +3 to +8
sudo apt-get update -y # Update apt-get cache
sudo apt-get install -y neofetch # Install curl

# install Node.js and npm
curl -sL https://deb.nodesource.com/setup_22.x | sudo -E bash
sudo apt-get install -y nodejs # Install Node.js and npm
Comment on lines +1 to +12
#!/bin/bash

sudo apt-get update -y # Update apt-get cache
sudo apt-get install -y neofetch # Install curl

# install Node.js and npm
curl -sL https://deb.nodesource.com/setup_22.x | sudo -E bash
sudo apt-get install -y nodejs # Install Node.js and npm

# Install Dependencies for all the section of this project
npm install --force && npm run build # Install & build dependencies for AxioDB main Codebase

Comment on lines +11 to +17
npm install --force && npm run build # Install & build dependencies for AxioDB main Codebase

# Install Dependencies for the AxioDB Documentation
cd ./Document && npm i --force && cd .. # Install & build dependencies for AxioDB Documentation

# Install Dependencies for the AxioDB GUI
cd ./GUI && npm i --force && cd .. # Install & build dependencies for AxioDB GUI
Comment on lines +6 to +11
# install Node.js and npm
curl -sL https://deb.nodesource.com/setup_22.x | sudo -E bash
sudo apt-get install -y nodejs # Install Node.js and npm

# Install Dependencies for all the section of this project
npm install --force && npm run build # Install & build dependencies for AxioDB main Codebase
"memory": "4gb" // 4gb is the minimum requirement for the universal image
},
// // Or use a Dockerfile or Docker Compose file. More info: https://containers.dev/guide/dockerfile
// "image": "mcr.microsoft.com/devcontainers/typescript-node:1-20-bullseye",
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants