galaxyproject / galaxyproject/training-material
Lint for input_histories/answer_histories to be archived
- Dominant language
- HTML
- Stars
- 367
- Forks
- 1.1k
- Avg merge
- 16h 27m
- Merged PRs (30d)
- 49
Description
if we can we easily tell from an e.g. API call (as anonymous external users) whether those histories are archived or not, we can add linting to ensure those histories are archived and prevent accidental modification/deletion.
_Originally posted by @hexylena in https://github.com/galaxyproject/training-material/issues/5395#issuecomment-2393115671_
Contributor guide
Research direction
Inspect the input_histories/ and answer_histories paths and determine whether an anonymous API call can identify archived histories. Define how linting should detect and prevent accidental modification or deletion, then verify the lint reports the relevant unarchived histories.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100