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 Feb 12, 2023. It is now read-only.
Is there a way to exclude individual files from linking?
As an example use case:
GitVersionTask injects an assemblyinfo into the final assembly
This is registered at the <project\obj\release\gitversiontaskassemblyinfo.g.cs path.
When GitLink builds it then warns that these files are missing (which is expected, and not a problem).
It would be nice to exclude them from the linking process with GitLink.
This is an issue as they then show up in the MSBuild warning list on† build logs, which is confusing when scanning the build console output for issues. It also therefore pollutes the output from CI servers with warnings that are not relevant.
†edit: not in the warning list, but it shows up as important messages which say "missing file" and look like warnings
The text was updated successfully, but these errors were encountered:
I think you can ignore projects, not files. The reason for this is probably because pdbstr will use a variable for the urls. However, I think that ignoring .g.cs files would be a good idea by default anyway.
Interested in doing a PR for this?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Is there a way to exclude individual files from linking?
As an example use case:
<project\obj\release\gitversiontaskassemblyinfo.g.cs
path.It would be nice to exclude them from the linking process with GitLink.
This is an issue as they then show up in the MSBuild
warning list on† build logs, which is confusing when scanning the build console output for issues. It also therefore pollutes the output from CI servers with warnings that are not relevant.† edit: not in the warning list, but it shows up as important messages which say "missing file" and look like warnings
The text was updated successfully, but these errors were encountered: