Shaman should contain (and sort by) a 'created' field
Open
- Dominant language
- Python
- Stars
- 8
- Forks
- 21
- Avg merge
- 3h 54m
- Merged PRs (30d)
- 2
Description
Currently, if a build is "updated", the `modified` field is updated, breaking the sort order.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing how Shaman represents builds and applies the current `modified` field when a build is updated. The work is done when builds also retain a `created` field and sorting uses that field so updates no longer change their sort order.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100