microsoft / microsoft/VFSForGit
Keep a list of known issues/behaviors in the VFSForGit repo
Open
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.1k
- Forks
- 474
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 8
Description
VFSForGit known issues are not easy to discover. Start a document that's kept in the repo and discoverable via the readme that tracks known issues/behaviors that are specific to VFS4G repos (e.g. projected folders cannot be renamed).
Contributor guide
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
Start with the repository README to determine where a known-issues document should be linked. Add a repository-hosted document covering VFSForGit-specific known issues and behaviors, including projected-folder rename limitations, and make it discoverable from the README.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100