|
| 1 | +# ModernWpf CI/CD documentation |
| 2 | + |
| 3 | +## 1. Set up Dependabot |
| 4 | + |
| 5 | +Dependabot is a GitHub native security tool that goes through the dependencies in the project and creates alerts, and PRs with updates when a new and/or non-vulnerable version is found. |
| 6 | + |
| 7 | +- for PRs with version updates, this pipeline comes pre-configured for all current dependency sources in the project, so at "Insights" tab -> "Dependency graph" -> "Dependabot", you should be able to see all tracked sources of dependencies, when they have been checked last and view a full log of the last check |
| 8 | + |
| 9 | + |
| 10 | + |
| 11 | + |
| 12 | + |
| 13 | +### Set up security alerts and updates |
| 14 | +##### - GitHub, through Dependabot, also natively offers a security check for vulnerable dependencies |
| 15 | + |
| 16 | +1. Go to the project's GitHub repository and click on the **Settings** tab |
| 17 | + |
| 18 | +2. Go to **Security & analysis** section |
| 19 | + |
| 20 | +3. Click "Enable" for both "Dependabot alerts" and "Dependabot security updates" |
| 21 | + |
| 22 | +- By enabling "Dependabot alerts", you would be notified for any vulnerable dependencies in the project. At "Security" tab -> "Dependabot alerts", you can manage all alerts. By clicking on an alert, you would be able to see a detailed explanation of the vulnerability and a viable solution. |
| 23 | + |
| 24 | + |
| 25 | + |
| 26 | + |
| 27 | + |
| 28 | +- By enabling "Dependabot security updates", you authorize Dependabot to create PRs specifically for **security updates** |
| 29 | + |
| 30 | + |
| 31 | + |
| 32 | +### Set up Dependency graph |
| 33 | +##### - The "Dependency graph" option should be enabled by default for all public repos, but in case it isn't: |
| 34 | + |
| 35 | +1. Go to the project's GitHub repository and click on the **Settings** tab |
| 36 | + |
| 37 | +2. Go to **Security & analysis** section |
| 38 | + |
| 39 | +3. Click "Enable" for the "Dependency graph" option |
| 40 | + |
| 41 | +- this option enables the "Insights" tab -> "Dependency graph" section -> "Dependencies" tab, in which all the dependencies for the project are listed, under the different manifests they are included in |
| 42 | + |
| 43 | + |
| 44 | + |
| 45 | +NOTE: **screenshots are only exemplary** |
| 46 | + |
| 47 | +<br> |
| 48 | + |
| 49 | +## 2. CodeQL |
| 50 | + |
| 51 | +CodeQL is GitHub's own industry-leading semantic code analysis engine. CodeQL requires no setup, because it comes fully pre-configured by us. |
| 52 | + |
| 53 | +To activate it and see its results, only a push commit or a merge of a PR to the default branch of your repository, is required. |
| 54 | + |
| 55 | +We've also configured CodeQL to run on schedule, so every day at 8:00AM UTC, it automatically tests the code. |
| 56 | + |
| 57 | +- you can see the results here at **Security** tab -> **Code scanning alerts** -> **CodeQL**: |
| 58 | + |
| 59 | + |
| 60 | + |
| 61 | +- on the page of each result, you can see an explanation of what the problem is and also one or more solutions: |
| 62 | + |
| 63 | + |
| 64 | + |
| 65 | +# |
| 66 | + |
| 67 | +Built with ❤ by [Pipeline Foundation](https://pipeline.foundation) |
0 commit comments