You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/index.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1023,7 +1023,7 @@ We have created a framework that automates the process of creating, testing, and
1023
1023
<details>
1024
1024
<summary>How we do it in PSModule</summary>
1025
1025
1026
-
Projects are based on the `Template-Action` repository template will automatically have the necessary workflows and configurations set up to automate the process of creating, testing, and deploying PowerShell based Azure Function Apps to Azure. This includes workflows for building, testing, and deploying the function app, as well as a configuration file for setting up the function app's metadata and dependencies.
1026
+
Projects based on the `Template-Action` repository template will automatically have the necessary workflows and configurations set up to automate the process of creating, testing, and deploying PowerShell based Azure Function Apps to Azure. This includes workflows for building, testing, and deploying the function app, as well as a configuration file for setting up the function app's metadata and dependencies.
1027
1027
Using custom properties we set `RepoType` to `FunctionApp`.
1028
1028
We use branch policies to control the flow of changes to the `main` branch, and we use labels to control the versioning of the module when a pull request is merged.
1029
1029
@@ -1141,7 +1141,7 @@ We use branch policies to control the flow of changes to the `main` branch, and
@@ -1345,14 +1345,14 @@ We use branch policies to control the flow of changes to the `main` branch, and
1345
1345
<summary>About</summary>
1346
1346
1347
1347
Reusable workflows are a way to define a workflow in one repository and use it in multiple repositories. They can be used to automate common tasks, such as building, testing, and deploying code, and they can help to streamline the development process by providing a consistent way to perform these tasks across multiple repositories.
1348
-
We have created a framework that automates the process of creating, testing, and deploying reusable workflows in a organization. This framework is designed to make it easy for developers to create and share their workflows with the community.
1348
+
We have created a framework that automates the process of creating, testing, and deploying reusable workflows in an organization. This framework is designed to make it easy for developers to create and share their workflows with the community.
1349
1349
1350
1350
</details>
1351
1351
1352
1352
<details>
1353
1353
<summary>How we do it in PSModule</summary>
1354
1354
1355
-
Projects are based on the `Template-Workflow` repository template will automatically have the necessary workflows and configurations set up to automate the process of creating, testing, and deploying reusable workflows in a organization. This includes workflows for building, testing, and deploying the workflows, as well as a configuration file for setting up the workflows metadata and dependencies.
1355
+
Projects based on the `Template-Workflow` repository template will automatically have the necessary workflows and configurations set up to automate the process of creating, testing, and deploying reusable workflows in an organization. This includes workflows for building, testing, and deploying the workflows, as well as a configuration file for setting up the workflow's metadata and dependencies.
1356
1356
Using custom properties we set `RepoType` to `Workflow`.
1357
1357
We use branch policies to control the flow of changes to the `main` branch, and we use labels to control the versioning of the module when a pull request is merged.
0 commit comments