Note history or blame log
Open
feature
- Dominant language
- JavaScript
- Stars
- 10.1k
- Forks
- 1.1k
- PR merge metrics
- No merged PRs in 30d
Description
To review note changes and revert.
It's necessary to have change history or blame log.
Contributor guide
Research direction
The issue names no files, tests, or entry points. Start by locating the note persistence and collaboration entry points, then determine the scope needed for reviewing changes and reverting a note; done means both change history or blame information and a working revert flow are defined and covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- full-stack
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100