Skip to content

Commit f01cee4

Browse files
committed
docs: Update ReadMes to mention Azure DevOps functions are coming later
1 parent d55cb76 commit f01cee4

File tree

2 files changed

+3
-4
lines changed

2 files changed

+3
-4
lines changed

ReadMe.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -76,7 +76,6 @@ Things to still do:
7676
- Add some badges as well to the ReadMe.
7777
- Look at improving GitHub issue and PR templates: https://raw.githubusercontent.com/PowerShell/vscode-powershell/main/.github/ISSUE_TEMPLATE/bug-report.yml
7878
- Update the module to be able to create new repos without using GitHub template. Have a New-PowerShellScriptModuleRepository cmdlet
79-
- For now remove the Azure DevOps components from the docs; will add it in once GitHub is working well.
8079
- To prevent having to store CI/CD manual setup images in the repo, maybe have them as an external link to a GitHub branch.
8180
- Also create videos showing how to do the setup.
8281
- Add a simple PowerShell devcontainer for both this repo and the template.

src/Template.PowerShell.ScriptModule/TemplateRepoFiles/ReadMe.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -24,13 +24,13 @@ Otherwise, use these files as a starting point for your new module.
2424
This template includes CI/CD workflows for building and publishing the PowerShell module using both GitHub Actions and Azure DevOps Pipelines.
2525
Follow the instructions for the CI/CD system you plan to use.
2626

27-
#### 🐙🐱 GitHub Actions
27+
#### GitHub Actions
2828

2929
If using GitHub Actions for your CI/CD workflows, perform the following steps:
3030

31-
#### ♻️ Azure DevOps Pipelines
31+
#### Azure DevOps Pipelines
3232

33-
If using Azure DevOps Pipelines for your CI/CD pipelines, perform the following steps:
33+
Coming soon.
3434

3535
### ✔ Step 5: Review and update boilerplate repo files
3636

0 commit comments

Comments
 (0)