mz/DiunaBI
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

P2 processor is working as a charm!
All checks were successful
Build Docker Images / test (map[name:Morska plugin_project:DiunaBI.Plugins.Morska]) (push) Successful in 1m23s
Details
Build Docker Images / test (map[name:PedrolloPL plugin_project:DiunaBI.Plugins.PedrolloPL]) (push) Successful in 1m28s
Details
Build Docker Images / build-and-push (map[image_suffix:morska name:Morska plugin_project:DiunaBI.Plugins.Morska]) (push) Successful in 1m40s
Details
Build Docker Images / build-and-push (map[image_suffix:pedrollopl name:PedrolloPL plugin_project:DiunaBI.Plugins.PedrolloPL]) (push) Successful in 1m37s
Details

Browse Source
This commit is contained in:
Michał Zieliński
2025-12-05 19:10:28 +01:00
parent 0eb2a457f7
commit 6b0f936f40
6 changed files with 663 additions and 45 deletions
Download Patch File Download Diff File Expand all files Collapse all files

37
.claude/commands/updateContext.md
View File

@@ -1,18 +1,27 @@
Re-explore the DiunaBI codebase comprehensively and update the `.claude/project-context.md` file with the latest:
Update the `.claude/project-context.md` file by ONLY appending changes made during THIS session to the "RECENT CHANGES (This Session)" section at the top of the file.
1. Project structure changes (new projects, folders, or major reorganization)
2. New features and functionality added
3. Database schema changes (new entities, significant field additions)
4. New API endpoints or controllers
5. New services or business logic components
6. Changes to authentication/authorization
7. New external integrations or plugins
8. Recent git commits (last 5-10) to understand development direction
9. Updated configuration or environment changes
10. New design patterns or architectural changes
**DO NOT re-scan or re-explore the entire codebase** - this wastes tokens and time.
Use the Task tool with subagent_type='Explore' and thoroughness level 'very thorough' to comprehensively analyze the codebase.
**What to do:**
After exploration, update the `.claude/project-context.md` file with all relevant changes while maintaining the existing structure and format. Preserve information that hasn't changed.
1. Review the conversation history to identify what was changed/added/fixed in THIS session
2. Read the current `.claude/project-context.md` file
3. Update ONLY the "RECENT CHANGES (This Session)" section at the top with:
- Date of changes (today's date)
- Brief bullet points describing what was modified
- Files that were changed with brief descriptions
- Any new functionality added
- Bug fixes completed
4. Leave the rest of the file unchanged
When done, provide a brief summary of what was updated in the context file.
**Format for session changes:**
```markdown
## RECENT CHANGES (This Session)
**[Feature/Fix Name] ([Date]):**
- ✅ Brief description of change 1
- ✅ Brief description of change 2
- Files modified: [file1.cs](path/to/file1.cs), [file2.cs](path/to/file2.cs)
```
When done, provide a brief summary of what session changes were documented.