Conversation
…ty attribute Co-authored-by: dkurepa <91743470+dkurepa@users.noreply.github.com>
docs/Darc.md
Outdated
| - If ALL dependencies from a repository have `SkipProperty="true"`, no repository header | ||
| comment will be generated in `Version.Details.props` | ||
|
|
||
| **When to use SkipProperty:** |
Co-authored-by: dkurepa <91743470+dkurepa@users.noreply.github.com>
docs/Darc.md
Outdated
| ```xml | ||
| <Import Project="Version.Details.props" Condition="Exists('Version.Details.props')" /> | ||
| ``` | ||
| 3. Run `darc update-dependencies` to regenerate version properties |
There was a problem hiding this comment.
@copilot you can also remove the steps 2. 3. 4. 5. Instead say that the file will be populated during the next dependency update, and that a merge policy will provide further instructions
There was a problem hiding this comment.
Done in 9c199d8. Simplified the migration steps to just creating an empty file, with a note that it will be populated automatically and the merge policy will provide further instructions.
Co-authored-by: dkurepa <91743470+dkurepa@users.noreply.github.com>
There was a problem hiding this comment.
Pull Request Overview
Updates Darc documentation to describe the new Version.Details.props file workflow and the SkipProperty attribute, and adjusts related command descriptions.
- Adds TOC entry and a dedicated section detailing Version.Details.props and SkipProperty.
- Updates add-dependency command description to reflect new property generation logic.
- Provides migration guidance from legacy Versions.props usage.
|
|
||
| When adding a new dependency, only name and type are required. For a detailed | ||
| discussion on adding new dependencies to a repository, see [Adding dependencies to a repository](#adding-dependencies-to-a-repository) | ||
| discussion on adding new dependencies to a repository, see [Adding dependencies to a repository](#adding-dependencies-to-a-repository). |
There was a problem hiding this comment.
The file name is incorrect; it should be Version.Details.xml (plural 'Details').
| discussion on adding new dependencies to a repository, see [Adding dependencies to a repository](#adding-dependencies-to-a-repository). | |
| Add a new tracked dependency to the Version.Details.xml file in your local repo. |
|
|
||
| See also [Version.Details.props and the SkipProperty attribute](#versiondetailsprops-and-the-skipproperty-attribute) | ||
| for information on how dependency properties are generated. | ||
|
|
There was a problem hiding this comment.
Capitalize GitHub properly.
| into the remote GitHub or AzDO repository, the dependency can be updated by Maestro++ |
|
|
||
| **Key characteristics:** | ||
| - **Auto-generated**: This file is created and maintained automatically by Maestro dependency flow. | ||
| - **Do not manually edit**: Changes will be overwritten by automation during dependency updates. |
There was a problem hiding this comment.
[nitpick] Consider adding an explicit note that Version.Details.props must be checked into source control (not gitignored) so automation can update it via PRs.
| - **Do not manually edit**: Changes will be overwritten by automation during dependency updates. | |
| - **Do not manually edit**: Changes will be overwritten by automation during dependency updates. | |
| - **Must be checked into source control**: This file **must not** be gitignored. It should be committed to your repository so that automation can update it via pull requests. |
Co-authored-by: Přemek Vysoký <premek.vysoky@microsoft.com>
Co-authored-by: Přemek Vysoký <premek.vysoky@microsoft.com>
Co-authored-by: Přemek Vysoký <premek.vysoky@microsoft.com>
Co-authored-by: Přemek Vysoký <premek.vysoky@microsoft.com>
SkipPropertydependencies #5209 changes to understand what was implementedOriginal prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.