Better handle no-op updates
Open
area/updates
enhancement
- Dominant language
- Rust
- Stars
- 2.3k
- Forks
- 230
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 38
Description
It's possible today to get a no-op update where e.g. just metadata like labels change. We should definitely detect this and highlight the no-op nature of the change; probably just default to "live updating" the origin? Should we record that transition at all though (just in the journal)?.
Contributor guide
Assessment
This issue has not been assessed yet.