dmainou opened a new issue, #6387:
URL: https://github.com/apache/hop/issues/6387
### What would you like to happen?
## Summary
Extend the Explorer’s Git integration so that users can **commit assets
other than workflows and pipelines**, including:
- Unit test JSON files
- Test datasets
- Golden sets / expected result files
- Reference and fixture data (e.g. readme files, etc)
These assets are a core part of hop and currently need to be committed in
terminal
---
## Problem
Today, the Explorer’s Git commit functionality is effectively **limited to
pipelines and workflows**.
However, real-world delivery relies on a wider set of artefacts:
| Asset type | Purpose |
|-----------|--------|
| Unit test JSON | Defines test scenarios |
| Test datasets | Input data for tests |
| Golden sets | Expected output used for assertions |
| Reference data | Controlled test fixtures |
These files:
- Live in the same project
- Are required to run tests
- Must stay in sync with pipelines
Yet they **cannot be committed from the Explorer**, forcing users to switch
to the command line or external Git clients
---
## Proposed Behaviour
The Explorer’s Git commit UI should allow users to:
- Select and commit **any file** in the project tree, not just:
- Pipelines
- Workflows
This includes:
- `.json`
- `.csv`
- `.parquet`
- `.txt`
- `.yaml`
- or any other test, dataset, or reference file
They should:
- Appear in the Git status view
- Be selectable
- Be staged and committed alongside pipelines
---
## Why this matters
Modern data engineering is **test-driven and Git-driven**.
Pipelines without their:
- Test cases
- Input data
- Golden outputs
are:
- Not reproducible
- Not reviewable
- Not safe to promote
This feature ensures:
- Tests and pipelines move together
- CI/CD remains deterministic
- Developers can refactor safely
- Audits and compliance are preserved
---
## Impact
This turns Explorer into a **true data engineering workspace**, not just a
pipeline editor.
It enables:
- Test-driven pipeline development
- Reliable CI/CD
- Professional Git workflows
- Full project-level version control
All without forcing users out of the UI.
### Issue Priority
Priority: 3
### Issue Component
Component: Hop Gui
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
