Any thoughts on commenting/write support?
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 20
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
This would be great for use on flights / offline times. Any thoughts on what you'd think about commenting or write support with sync when access is restored?
If that seems like a lot of work, or out of original scope - what if this was contributed by a third-party?
Thanks,
Alex
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.
Research direction
The issue does not name files, tests, or an entry point. Start by reviewing the repository's existing offline GitHub Issues Client behavior, then clarify the intended commenting or write operations and how synchronization should work when access returns. Done criteria would need to define the supported offline changes and their sync behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100