microsoftgraph / microsoftgraph/msgraph-sdk-dotnet
Request for more meaningful release notes
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 789
- Forks
- 264
- Avg merge
- 15h 17m
- Merged PRs (30d)
- 3
Description
Most time, the code changes in this project are auto generated by some external process. I have the impression that the release notes of this process changed during the last months. Earlier, it was sometimes possible to find out what was changed in a certain release. But nowadays, the commit "update request builders and models" does not contain any detail information on the changes and no link to resolved issues.
Is it possible to create release notes that contain information on the underlying changes?
Or could you at least provide a link to the changelog for the part that caused the "update request builders and models" commit?
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
The issue names no file, test, or entry point. Start by tracing the external process that generates release notes and compare its current output with earlier releases, especially for the “update request builders and models” commit. Done means the release notes provide underlying change details or link to the relevant changelog and resolved issues.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, release
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100