e2e: assert a clean tree after every command
- Dominant language
- Python
- Stars
- 1
- Forks
- 4
- Avg merge
- 15h 39m
- Merged PRs (30d)
- 24
Description
Every mechababs transition is a `datalad run --explicit`, which saves only the declared outputs and silently leaves anything else dirty. Nothing is dirty today; this is preemptive.
A `git status --porcelain` check at the study and at the superstudy (`--ignore-submodules=none`) after each scenario step would catch a new file we forgot to declare before it lands on a real campaign, where the next iterate refuses the dirty tree and blames the operator. Cheap: one helper in the suite, run after every dispatch.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Contributor guide
No contributing guide indexed for this repository
Research direction
Start in the e2e suite around the scenario-step dispatches; the issue does not name a file or test entry point. Add the shared post-dispatch checks at both the study and superstudy levels, using git status --porcelain and --ignore-submodules=none for the superstudy. Done means every scenario step verifies both trees are clean.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, python
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 72/100