-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
6 additions
and
9 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,29 +1,26 @@ | ||
| # Simple Flow | ||
|
|
||
| This scenario shows how to generate `.diff` files for a few repositories for the actual PKUP period in the acctual directory. | ||
| This scenario shows how to generate `.diff` files for a few repositories for the actual PKUP period in the actual directory. | ||
|
|
||
| 1. Construct `pkup-gen` spell with most basic flags: | ||
| 1. Construct the `pkup-gen` spell with the most basic flags: | ||
|
|
||
| ```bash | ||
| pkup gen --username "<GITHUB_USERNAME>" --repo "<ORG>/<REPO>" | ||
| ``` | ||
|
|
||
| > Example: pkup gen --username "pPrecel" --repo "kyma-project/serverless-manager" | ||
|
|
||
| 2. Because PAT token is not provided, `pkup-gen` try to connect to the GitHub app to create one - here follow the instructions in the `WARN` log: | ||
|
|
||
|  | ||
|
|
||
| 3. On GitHub side you have to pass copied code and click `Continue` and then `Authorize pkup-gen`: | ||
| 2. Because PAT is not provided, `pkup-gen` tries to connect to the GitHub app to create one - here follow the instructions in the `WARN` log: | ||
|
|
||
| ![1]On the GitHub side you have to pass the copied code, click `Continue` and then `Authorize pkup-gen`: | ||
|  | ||
|  | ||
|
|
||
| 4. Now `pkup-gen` continues to generate artifacts what is represented in logs: | ||
| 3. Now `pkup-gen` continues to generate artifacts that are represented in logs: | ||
|
|
||
|  | ||
|
|
||
| 5. At the end you can see a few new files generated in the acctual directory and the `.txt` file with all info to manually fill `.docx` report: | ||
| 4. At the end you can see a few new files generated in the actual directory and the `.txt` file with all the info to manually fill the `.docx` report: | ||
|
|
||
|  | ||
|  |