You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 25, 2022. It is now read-only.
The update machinery for .NET packages is set up in such a way that when Microsoft releases a new SDK "feature band" (.1xx, .2xx etc.) a new package is automatically generated from a template. Unfortunately, the Git plugin only adds modified files. As a consequence, the new package is generated, packed and pushed to chocolatey.org, but not committed to the repo, requiring manual syncing up later.
Would you accept a PR with a switch for the Git plugin enabling adding of new files?
The text was updated successfully, but these errors were encountered:
The update machinery for .NET packages is set up in such a way that when Microsoft releases a new SDK "feature band" (.1xx, .2xx etc.) a new package is automatically generated from a template. Unfortunately, the Git plugin only adds modified files. As a consequence, the new package is generated, packed and pushed to chocolatey.org, but not committed to the repo, requiring manual syncing up later.
Would you accept a PR with a switch for the Git plugin enabling adding of new files?
The text was updated successfully, but these errors were encountered: