removed screenshots from documentation

This commit is contained in:
melody-universe 2021-06-30 22:36:43 -07:00
Родитель 71215e601e
Коммит dbb1062da2
5 изменённых файлов: 3 добавлений и 23 удалений

1
.gitattributes поставляемый
Просмотреть файл

@ -1,3 +1,2 @@
pac/**/* filter=lfs diff=lfs merge=lfs -text
/readme-assets/**/* filter=lfs diff=lfs merge=lfs -text
pac/**/*.* filter=lfs diff=lfs merge=lfs -text

Просмотреть файл

@ -18,7 +18,6 @@ This project provides a starting point for applying ALM best practices to your P
## Setup
1. Either fork this repository or [use it as a template](https://github.com/microsoft/power-apps-portals-alm/generate).
![Screenshot creating a new public repository using this one as a template](./readme-assets/create-repository-from-template.png)
- **Note:** Because this project uses [environments](https://docs.github.com/en/actions/reference/environments), you must create either a public repository or a private repository for GitHub Enterprise.
2. Set up the environments in your repository (outlined below):
1. From your repository home page, click **Settings**.
@ -41,19 +40,10 @@ This project provides a starting point for applying ALM best practices to your P
5. Repeat steps ii-iv to create the following secrets:
- **CLIENT_SECRET**: A client secret for your application user, e.g. _1f7~GP48Pi17T-R.4uyIU7_kOiV2NCnH_Q_.
- **TENANT_ID**: The Directory (tenant) ID that your development environment is provisioned in, e.g. _fedcba98-7654-3210-fedc-ba9876543210_.
When you're finished with steps 2-3, your Secrets page should look like one of the following:
- If you are using a single application user for both environments:
![Screenshot of Secrets page with two environment secrets and three repository secrets](./readme-assets/one-application-user-secrets.png)
- If you are using one application user per environment:
![Screenshot of Secrets page with eight environment secrest and no repository secrets](./readme-assets/two-application-users-secrets.png)
4. Run the **Provision Dev** workflow (outlined below):
1. Click **Actions**.
2. Click **Provision Dev**.
3. Click **Run workflow** > **Run workflow**.
1. Click **Actions**.
2. Click **Provision Dev**.
3. Click **Run workflow** > **Run workflow**.
5. (Optional) Using the same steps outlined in step 4, run the **CI/CD** workflow.
## Contributing

Просмотреть файл

@ -1,3 +0,0 @@
version https://git-lfs.github.com/spec/v1
oid sha256:2816a98fe99ea7ba037ccd22ffcf9d7e68318d7352538e0c429f36cde048e3ce
size 130878

Просмотреть файл

@ -1,3 +0,0 @@
version https://git-lfs.github.com/spec/v1
oid sha256:f433a1071ae70d50cdb3aac96923fa1ab302ba271e0a94150dfb69bac77ecedd
size 88866

Просмотреть файл

@ -1,3 +0,0 @@
version https://git-lfs.github.com/spec/v1
oid sha256:54f66339ee651353a25aafb3d4f2c1a9d1ab8360497ab1fff9c740a66d2a86f4
size 179406