chore: Update branch references and add Conductor file exclusion policy
This commit is contained in:
10
GEMINI.md
10
GEMINI.md
@@ -48,9 +48,9 @@ The frontend is a modern SPA (Single Page Application) designed for data-heavy i
|
||||
- **LangChain Docs**: See the `langchain-docs/` folder for local LangChain and LangGraph documentation.
|
||||
|
||||
## Git Operations
|
||||
- All new feature and bug-fix branches must be created from the `conductor` branch except hot-fix.
|
||||
- The `conductor` branch serves as the primary development branch where integration occurs.
|
||||
- All new feature and bug-fix branches must be created from the `develop` branch except hot-fix.
|
||||
- The `develop` branch serves as the primary development branch where integration occurs.
|
||||
- The `main` branch is reserved for stable, production-ready code.
|
||||
- Merges from `conductor` to `main` should only occur when significant milestones are reached and stability is verified.
|
||||
- Conductor-specific configuration or meta-files should remain on the `conductor` branch or its derivatives and never be merged into the `main` branch.
|
||||
- Use rebase to keep commit history clean before merging feature branches back into `conductor`.
|
||||
- Merges from `develop` to `main` should only occur when significant milestones are reached and stability is verified.
|
||||
- **CRITICAL:** Conductor-specific configuration or meta-files (e.g., `conductor/` directory) must **NEVER** be tracked or committed to the repository. They are intended for local agent guidance and coordination only.
|
||||
- Use rebase to keep commit history clean before merging feature branches back into `develop`.
|
||||
|
||||
Reference in New Issue
Block a user