microsoft / microsoft/microsoft-performance-toolkit-sdk
Decouple projects versioning and set up proper path filtering in version files based on dependency
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 239
- Forks
- 78
- Avg merge
- 4d 3h
- Merged PRs (30d)
- 2
Description
Currently in our repository, a commit to a given project's (except for projects in the PluginsSystem folder) subtree will result in the version bumping for all projects. This is not desirable. We should set up proper versioning rules based on the dependencies and prevent unnecessary version changes.
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
Start by locating the version files and the automation that reacts to project-subtree commits, then trace how dependencies are represented; pay particular attention to the exception for the PluginsSystem folder. Define dependency-based path rules and verify that an isolated project change no longer bumps unrelated projects.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- build-system, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100