💡feat(TfsNodeStructureTool): Enhance logging for node migration process #2654
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…process Enhance logging to provide more detailed information about the node migration process. This includes logging the state of the ReplicateAllExistingNodes option and whether node migration is skipped or executed. The change improves traceability and debugging by providing clear insights into the execution flow and decisions made during the process.
|
Azure Static Web Apps: Your stage site is ready! Visit it here: https://blue-river-093197403-2654.westeurope.5.azurestaticapps.net |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
💡 (TfsNodeStructureTool.cs): add detailed logging for node migration process
Enhance logging to provide more detailed information about the node migration process. This includes logging the state of the ReplicateAllExistingNodes option and whether node migration is skipped or executed. The change improves traceability and debugging by providing clear insights into the execution flow and decisions made during the process.