Microsoft GitHub orgs/users not verified
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 166
- Forks
- 267
- Avg merge
- 2h 32m
- Merged PRs (30d)
- 2
Description
Multiple Microsoft GitHub organizations are not verified.
List:
https://github.com/MicrosoftDocs
https://github.com/MicrosoftLearning
https://github.com/Microsoft365DSC
https://github.com/AzureAD
https://github.com/MicrosoftEdge
https://github.com/microsoftgraph
https://github.com/Microsoft-corp (used for GitHub authentication to access a Microsoft account.)
NOTE: This user: https://github.com/microsoftopensource has Microsoft as their organization, but aren't a public member, and they need to do @Microsoft (GitHub uses @org and not just org for this!)
NOTE: This user:
https://github.com/msftgits has Microsoft as their organization, but aren't a public member, and they need to do @Microsoft (GitHub uses @org and not just org for this!)
https://github.com/MicrosoftCopilot (kinda more GitHub-iy)
https://github.com/microsoft-foundry
https://github.com/OfficeDev
https://github.com/MicrosoftResearch
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
Review the listed GitHub organizations and the notes about @Microsoft membership, starting with the verification status of each account. Done means the applicable organizations and users are verified, or the list clearly records any remaining blockers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- authentication
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100