Prevent relink from deleting original if GDEX copy doesn't match exactly
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
No files, tests, or entry points are identified. Start by locating the relink operation and how it compares a GDEX copy with the original; done means relink does not delete the original when the copies do not match exactly.
Written by the indexing model from the issue text.
Description
This could eventually be unnecessary if #26 is implemented and then all existing files are relinked, but it's impossible to say if or when that would ever happen.
- Dominant language
- Python
- Stars
- 0
- Forks
- 2
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 2
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ESMCI/inputdataTools
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
ESMCI/inputdataTools#30 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
ESMCI/inputdataTools#32 ·
-
bug
ESMCI/inputdataTools#29 · 1 assignee ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
ESMCI/inputdataTools#26 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
ESMCI/inputdataTools#24 ·
All issues in ESMCI/inputdataTools
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100