-
Notifications
You must be signed in to change notification settings - Fork 123
New issue
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
What are the extensibility points of these targets? #188
Comments
Any target or property whose name does not start with |
Thanks, @tmat. I know these are still pre-release versions. I'm trying to use the information collected by these targets to add them to the NuGet package information. For that, I need:
I guess that, apart from Shouldn't This NuGet blog post mentions these packages and links to the Pack target documentation which contains I'm also adding this information to assembly metadata and don't want to be collecting it again and risk being out of sync. |
Except for Do you need it for scenarios where you can't use .NET SDK? If so you can see how the above targets do it. |
The .NET SDK would also fill the I think it's worth the effort. Don't you think? Can I help? I'm also adding all this information to the assembly as And I'm fiddling with the repository URL and changing it to the commit URL. That way, on the NuGet site, the link goes directly to that commit. |
I'm gonna close this issue. If you think we should add support for |
Why doesn't RepositoryBranch get set? |
I'd like to extend these targets and I'd like to know what can I rely on and what the extensibility points are.
The text was updated successfully, but these errors were encountered: