Здравствуйте, mogadanez, Вы писали:

M>Здравствуйте, bnk, Вы писали:

bnk>>Сорри я про жиру условно написал, чтобы понятно было понятно о чем речь.
bnk>>Сам сейчас ее не использую.

M>ну условная жира, просто интересно как он там может там авторизоватся

В Az CLI есть команда az login (один раз), после этого все последующие выполняются без авторизации (оно тебя запоминает).

	Выглядит как-то так

Содержимое copilot-instructions чтобы это работало

	под катом
	## Azure DevOps CLI Configuration The project uses Azure DevOps for work item tracking and project management. ### Connection Details — **Organization URL**: `https://dev.azure.com/xxxxx` — **Primary Project**: `XXXXX` — **Team**: `XXXX Team` ### CLI Commands ```powershell # Configure default organization az devops configure --defaults organization=https://dev.azure.com/visto # List projects az devops project list --org https://dev.azure.com/visto --output table # Query assigned work items in current iteration az boards query --wiql "SELECT [System.Id], [System.Title], [System.State], [System.WorkItemType], [System.IterationPath] FROM WorkItems WHERE [System.AssignedTo] = @Me AND [System.IterationPath] = @CurrentIteration('[Visto]\Visto Team') AND [System.State] <> 'Closed' AND [System.State] <> 'Removed' ORDER BY [System.ChangedDate] DESC" --org https://dev.azure.com/visto --project "Visto" --output table # Query all assigned work items (any state except Closed/Removed) az boards query --wiql "SELECT [System.Id], [System.Title], [System.State], [System.WorkItemType] FROM WorkItems WHERE [System.AssignedTo] = @Me AND [System.State] <> 'Closed' AND [System.State] <> 'Removed' ORDER BY [System.ChangedDate] DESC" --org https://dev.azure.com/visto --project "Visto" --output table # Add a comment to a work item (visible in Discussion tab) # Use System.History field with HTML formatting for proper visibility in the UI # IMPORTANT: Do NOT use "Fixed:" prefix as it auto-closes items. Use "Resolved:" instead. # Items should go to "Resolved" state for test team verification, not directly to "Fixed/Closed" # CRITICAL: Always write comments in NON-TECHNICAL language that testers can understand # Focus on what was broken, what was fixed, and how to test it — avoid implementation details az boards work-item update --id <work-item-id> --org https://dev.azure.com/visto --fields "System.History=<html-formatted-comment>" # Example with proper formatting (non-technical language): az boards work-item update --id 725 --org https://dev.azure.com/visto --fields "System.History=Resolved: Fixed the issue where XYZ was not working.<br/><br/><b>What was broken:</b><br/>Description of the problem from user perspective<br/><br/><b>What was fixed:</b><br/>Description of the solution from user perspective<br/><br/><b>How to test:</b><br/>1. Step-by-step testing instructions<br/>2. What to verify<br/><br/>Commit: abc1234" # Note: Using --discussion parameter does NOT create visible comments in the UI # Always use System.History field for comments that should appear in the Discussion tab # Workflow: Development -> Resolved (for testing) -> Closed/Fixed (after verification) # Use "Resolved:" prefix so test team can verify before marking as "Fixed" ```

Здравствуйте, mogadanez, Вы писали:

M>Здравствуйте, bnk, Вы писали:

bnk>>Сорри я про жиру условно написал, чтобы понятно было понятно о чем речь.
bnk>>Сам сейчас ее не использую.

M>ну условная жира, просто интересно как он там может там авторизоватся

В Az CLI есть команда az login (один раз), после этого все последующие выполняются без авторизации (оно тебя запоминает).

	Выглядит как-то так

Содержимое copilot-instructions чтобы это работало

	под катом
	## Azure DevOps CLI Configuration The project uses Azure DevOps for work item tracking and project management. ### Connection Details — **Organization URL**: `https://dev.azure.com/xxxxx` — **Primary Project**: `XXXXX` — **Team**: `XXXX Team` ### CLI Commands ```powershell # Configure default organization az devops configure --defaults organization=https://dev.azure.com/xxxx # List projects az devops project list --org https://dev.azure.com/xxxx --output table # Query assigned work items in current iteration az boards query --wiql "SELECT [System.Id], [System.Title], [System.State], [System.WorkItemType], [System.IterationPath] FROM WorkItems WHERE [System.AssignedTo] = @Me AND [System.IterationPath] = @CurrentIteration('[XXXX]\XXXX Team') AND [System.State] <> 'Closed' AND [System.State] <> 'Removed' ORDER BY [System.ChangedDate] DESC" --org https://dev.azure.com/xxxx --project "XXXX" --output table # Query all assigned work items (any state except Closed/Removed) az boards query --wiql "SELECT [System.Id], [System.Title], [System.State], [System.WorkItemType] FROM WorkItems WHERE [System.AssignedTo] = @Me AND [System.State] <> 'Closed' AND [System.State] <> 'Removed' ORDER BY [System.ChangedDate] DESC" --org https://dev.azure.com/xxxx --project "XXXX" --output table # Add a comment to a work item (visible in Discussion tab) # Use System.History field with HTML formatting for proper visibility in the UI # IMPORTANT: Do NOT use "Fixed:" prefix as it auto-closes items. Use "Resolved:" instead. # Items should go to "Resolved" state for test team verification, not directly to "Fixed/Closed" # CRITICAL: Always write comments in NON-TECHNICAL language that testers can understand # Focus on what was broken, what was fixed, and how to test it — avoid implementation details az boards work-item update --id <work-item-id> --org https://dev.azure.com/xxxx --fields "System.History=<html-formatted-comment>" # Example with proper formatting (non-technical language): az boards work-item update --id 725 --org https://dev.azure.com/xxxx --fields "System.History=Resolved: Fixed the issue where XYZ was not working.<br/><br/><b>What was broken:</b><br/>Description of the problem from user perspective<br/><br/><b>What was fixed:</b><br/>Description of the solution from user perspective<br/><br/><b>How to test:</b><br/>1. Step-by-step testing instructions<br/>2. What to verify<br/><br/>Commit: abc1234" # Note: Using --discussion parameter does NOT create visible comments in the UI # Always use System.History field for comments that should appear in the Discussion tab # Workflow: Development -> Resolved (for testing) -> Closed/Fixed (after verification) # Use "Resolved:" prefix so test team can verify before marking as "Fixed" ```