Skip to content

[WIP] Refactor repository to create foundry_erp app - #6

Draft
PATILYASHH with Copilot wants to merge 1 commit into
mainfrom
copilot/refactor-to-foundry-erp-app
Draft

[WIP] Refactor repository to create foundry_erp app#6
PATILYASHH with Copilot wants to merge 1 commit into
mainfrom
copilot/refactor-to-foundry-erp-app

Conversation

Copilot AI commented Jan 9, 2026

Copy link
Copy Markdown
Contributor

Refactor Repository to Foundry ERP Frappe App

Plan:

  • Create standard Frappe app directory structure
    • Create foundry_erp/foundry_erp/ directories
    • Add __init__.py files
    • Create hooks.py with proper configuration
    • Create modules.txt file
  • Create pyproject.toml with proper dependencies
    • Set Python version to >=3.10
    • Add frappe ~=15.0 dependency
    • Add erpnext dependency
  • Create proper Frappe app metadata files
    • Create license.txt
    • Create README.md for the app
  • Update .gitignore to exclude Frappe-specific files
  • Verify the app structure is valid for bench get-app installation
Original prompt

You are refactoring this repository into a proper custom Frappe app named "foundry_erp".

CRITICAL RULES:

  • DO NOT rename or modify ERPNext core logic.
  • DO NOT globally replace "erpnext" imports.
  • This must become a standalone Frappe app that DEPENDS on ERPNext.

TASKS:

  1. Ensure the repository follows standard Frappe app structure:

    • foundry_erp/
      • foundry_erp/
        • init.py
        • hooks.py
        • modules.txt
      • pyproject.toml
  2. Update hooks.py so:

    • app_name = "foundry_erp"
    • app_title = "Foundry ERP"
    • app_publisher reflects Foundry ERP
    • Remove ERPNext scheduler, routes, website rules, assets, and core hooks
  3. Remove all ERPNext-specific assets, schedulers, routes, patches, and doctypes.
    Only keep Foundry-related doctypes, scripts, fixtures, and business logic.

  4. Ensure pyproject.toml:

    • requires-python = ">=3.10"
    • frappe dependency = "~=15.0"
    • erpnext is listed as a dependency
  5. Ensure no imports like "import erpnext.*" remain unless required for extension.
    Foundry logic should extend ERPNext, not replace it.

  6. After refactor, the app must be installable via:
    bench get-app
    bench --site install-app foundry_erp

STOP and report if ERPNext core files are still present.


💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

@vercel

vercel Bot commented Jan 9, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Review Updated (UTC)
bcsnotes Ready Ready Preview, Comment Jan 9, 2026 6:08am
gst-calculator Ready Ready Preview, Comment Jan 9, 2026 6:08am
machine-learning-notes Ready Ready Preview, Comment Jan 9, 2026 6:08am

@netlify

netlify Bot commented Jan 9, 2026

Copy link
Copy Markdown

Deploy Preview for mlnotesnck failed.

Name Link
🔨 Latest commit a96d2f0
🔍 Latest deploy log https://app.netlify.com/projects/mlnotesnck/deploys/69609b5298d6fd00083265ff

@netlify

netlify Bot commented Jan 9, 2026

Copy link
Copy Markdown

Deploy Preview for bcsml failed. Why did it fail? →

Name Link
🔨 Latest commit a96d2f0
🔍 Latest deploy log https://app.netlify.com/projects/bcsml/deploys/69609b52e084c000080b2c46

@netlify

netlify Bot commented Jan 9, 2026

Copy link
Copy Markdown

Deploy Preview for thriving-valkyrie-338dd1 failed. Why did it fail? →

Name Link
🔨 Latest commit a96d2f0
🔍 Latest deploy log https://app.netlify.com/projects/thriving-valkyrie-338dd1/deploys/69609b52e084c000080b2c4a

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants