We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is there any chance to generate a changelog when metadata are changed?
As a developer I've no idea what exactly was added or removed.
The only way is to check pull requests for SDKs, but pull requests have changes in thousands of files
https://github.com/microsoftgraph/msgraph-sdk-dotnet/pull/2521/files https://github.com/microsoftgraph/msgraph-sdk-dotnet/pull/2530/files
The changelog can help me decide whether to update to a new version or not.
The most frequent changes are in the comments, so changes in the comments do not have to be mentioned in the changelog.
The comments are the things where the most mistakes are visible at first glance. Obviously, no one is checking the changes.
Updating the .NET SDK takes seconds, but in case of PowerShell SDK, it takes (tens of) minutes
The text was updated successfully, but these errors were encountered:
If it's not related to this repo, I will probably close it.
Sorry, something went wrong.
No branches or pull requests
Is there any chance to generate a changelog when metadata are changed?
As a developer I've no idea what exactly was added or removed.
The only way is to check pull requests for SDKs, but pull requests have changes in thousands of files
https://github.com/microsoftgraph/msgraph-sdk-dotnet/pull/2521/files
https://github.com/microsoftgraph/msgraph-sdk-dotnet/pull/2530/files
The changelog can help me decide whether to update to a new version or not.
The most frequent changes are in the comments, so changes in the comments do not have to be mentioned in the changelog.
The comments are the things where the most mistakes are visible at first glance. Obviously, no one is checking the changes.
Updating the .NET SDK takes seconds, but in case of PowerShell SDK, it takes (tens of) minutes
The text was updated successfully, but these errors were encountered: