devise a consistent and documented strategy for pushing and applying the patch
Open
- Dominant language
- Java
- Stars
- 12
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
should we store patches with no context (0 lines), or N lines of context? (which N)?
should we apply patches based on line numbers? context? both? using a fuzz factor?
the goal is be able to directly use the patch on Defects4J
Contributor guide
No contributing guide indexed for this repository
Research direction
Review the repository's current patch-pushing and patch-applying behavior, then compare it with the patch format expected by Defects4J. Resolve whether patches should contain context and whether application should use line numbers, context, or fuzzing. Done means the strategy is consistent, documented, and directly usable on Defects4J.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- testing, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100