microsoft / microsoft/MSBuildSdks
Artifacts: Discrepancy between single- and multi-targeting scenarios
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 508
- Forks
- 94
- Avg merge
- 6h 40m
- Merged PRs (30d)
- 2
Description
This PR https://github.com/microsoft/MSBuildSdks/pull/227 added more knobs to the single-targeting branch, but not the multi-targeting branch.
Is richer than this:
https://github.com/microsoft/MSBuildSdks/blob/28c42cc282731aa69920a1f0582cfaba814315d2/src/Artifacts/buildMultiTargeting/Microsoft.Build.Artifacts.targets#L31-L33
Should we perhaps unify?
@jeffkl
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
Compare src/Artifacts/build/Microsoft.Build.Artifacts.targets with src/Artifacts/buildMultiTargeting/Microsoft.Build.Artifacts.targets at the referenced lines, then review PR #227 to identify the added single-targeting knobs. Done means determining whether the branches should be unified and aligning the multi-targeting branch if that is the agreed direction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100