Repository navigation
RFC: Core Architecture Refactor Before Merge/Remote Features #45
Leonardo-Garzon-1995
started this conversation in
Development/Design
Replies: 2 comments
|
New project structure for refactor |
0 replies
Refactor:
|
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Overview
As mygit grows, we are starting to reach the point where more advanced Git features (merge, fetch, push, remote tracking, etc.) will require a cleaner internal architecture.
The current implementation works well for the existing command set, but some duplication and structural inconsistencies have naturally appeared as the project expanded.
This discussion is intended to propose a refactor focused on maintainability and scalability — not a rewrite of existing functionality.
Goals
Important
This refactor is NOT intended to invalidate or replace contributor work.
The goal is:
Where possible:
Proposed Direction
Possible structure:
core/commands/services/utils/Areas That Probably Need Consolidation
Questions For Contributors
All reactions