Change VSO comments to GitHub issues
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 11.1k
- Forks
- 1.7k
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 22
Description
I think it should be a part of GitHub migration to migrate all VSO issues; but I think the ones mentioned in TRANSITION comments should be prioritized, and corresponding comments should be updated.
If some issue should not be migrated, probably a short description in TRANSITION comment should be added.
An example I've encountered today:
https://github.com/microsoft/STL/blob/88332706f49d3297b200b5605ef174fc47d38d1a/stl/inc/xmemory#L68-L71
I think I want to understand what exactly TRANSITION means here.
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 TRANSITION comment in stl/inc/xmemory at lines 68–71 and determine what it refers to. Review the repository for similar TRANSITION comments, then identify which VSO issues should become GitHub issues and which comments need updating or an explanation for omission. Done means the prioritized references and corresponding comments have been handled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100