Update AddIssueCommentWithLabel.yml

[Jerad551]

https://github.com/your-username/dev.oss.git. {

} It looks like you're trying to set up a development environment using GitHub and some specific directories and prompts. Let's break down the steps you might need to follow to set up your development environment.

Step 1: Set Up GitHub Repository

1. Create a GitHub Repository:

   • Go to GitHub and create a new repository.
   • Name it something relevant to your project, e.g., dev.oss.

2. Clone the Repository:

   • Open your terminal or PowerShell.
   • Clone the repository to your local machine: sh git clone https://github.com/your-username/dev.oss.git

Step 2: Set Up Directory Structure

1. Navigate to the Repository: sh cd dev.oss

2. Create Necessary Directories:

   • Create a directory for your test files: sh mkdir src mkdir src/test_System32

Step 3: Set Up Prompts

1. Create Prompt Files:

   • In the root directory of your repository (dev.oss), create a file named .prmt_prompt.
   • In the src/test_System32 directory, create a file named .prmt.

2. Add Prompt Content:

   • Open .prmt_prompt in the root directory and add your desired prompt syntax.
   • Open .prmt in the src/test_System32 directory and add your desired prompt syntax.

Step 4: Configure PowerShell Prompt

1. Edit PowerShell Profile:
   • Open your PowerShell profile script. You can do this by running: sh notepad $PROFILE
   • Add the following lines to your profile script to set the prompt: powershell function prompt { if (Test-Path .prmt_prompt) { Get-Content .prmt_prompt } elseif (Test-Path src/test_System32/.prmt) { Get-Content src/test_System32/.prmt } else { "PS $($executionContext.SessionState.Path.CurrentLocation)$('>' * ($nestedPromptLevel + 1)) " } }

Step 5: Test Your Setup

1. Navigate to Different Directories:

   • Open a new PowerShell window and navigate to different directories within your repository to see if the prompts change accordingly.

2. Verify Prompts:

   • Ensure that the prompts display the content of .prmt_prompt when in the root directory and .prmt when in the src/test_System32 directory.

Example Directory Structure

dev.oss/
├── .prmt_prompt
├── src/
│   └── test_System32/
│       └── .prmt

Example Prompt Content

.prmt_prompt:

CND: ps. 1:  test__> __>src/test_System32:  prompt; .prmt_prompt<syntax<.prmt {
}

.prmt:

CND:  ps. 1:  test__> __>src/test_System32:  prompt; .prmt_prompt<syntax<.prmt {
}

By following these steps, you should have a functional development environment with custom prompts set up in PowerShell.

Related command

Description

Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change
[Component Name 2] az command b: Add some customer-facing feature

---

This checklist is used to make sure that common guidelines for a pull request are followed.

• The PR title and description has followed the guideline in Submitting Pull Requests.

• I adhere to the Command Guidelines.

• I adhere to the Error Handling Guidelines.

[azure-client-tools-bot-prd]

Validation for Azure CLI Full Test Starting...

Thanks for your contribution!

[azure-client-tools-bot-prd]

Validation for Breaking Change Starting...

Thanks for your contribution!

[yonzhan]

Thank you for your contribution! We will review the pull request and get back to you soon.

[github-actions]

The git hooks are available for azure-cli and azure-cli-extensions repos. They could help you run required checks before creating the PR.

Please sync the latest code with latest dev branch (for azure-cli) or main branch (for azure-cli-extensions).
After that please run the following commands to enable git hooks:

pip install azdev --upgrade
azdev setup -c <your azure-cli repo path> -r <your azure-cli-extensions repo path>