summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAdonais Romero González <[email protected]>2023-03-21 15:44:51 -0700
committerAdonais Romero González <[email protected]>2023-03-21 15:44:51 -0700
commitff0188002091d91e1f36ac2e669ebaf1257e85d2 (patch)
treeb0406bf5109017e6870e6b1d9c8ea7ef13d79b55
parent5c3b6ca03ceead17b8729f4dbdbc479a4fc81274 (diff)
parentb9047602cf1d918e977e572f085df5bf973f9629 (diff)
Merge branch 'main' into develop
-rw-r--r--.github/Build-with-GitHub.md4
-rw-r--r--README.md2
2 files changed, 4 insertions, 2 deletions
diff --git a/.github/Build-with-GitHub.md b/.github/Build-with-GitHub.md
index 8fe67c5f..c4a10962 100644
--- a/.github/Build-with-GitHub.md
+++ b/.github/Build-with-GitHub.md
@@ -2,10 +2,10 @@
If you use GitHub to host your code, you can leverage [GitHub Actions](https://docs.github.com/en/actions) to create automated workflows to build your driver projects.
-`windows-2022` runner (provided by `windows-latest`) is configured with Windows Driver Kit version 22H2 and Visual Studio 2022 off the box, so most solutions can be built directly running `msbuild` directly.
+`windows-2022` runner (provided by `windows-latest`) is configured with Windows Driver Kit version 22H2 and Visual Studio 2022 off the box, so most solutions can be built by running `msbuild` directly.
```yaml
-name: Build all driver samples
+name: Build driver solution
on:
push:
branches:
diff --git a/README.md b/README.md
index 2e55d980..efd1e633 100644
--- a/README.md
+++ b/README.md
@@ -46,6 +46,8 @@ If you're writing your first driver, use these exercises to get started. Each ex
[Write a KMDF driver based on a template](https://docs.microsoft.com/windows-hardware/drivers/gettingstarted/writing-a-kmdf-driver-based-on-a-template)
+[Use GitHub Actions to build a simple driver project](.github/Build-with-GitHub.md)
+
# Microsoft Code of Conduct
This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/). For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or contact [[email protected]](mailto:[email protected]) with any additional questions or comments.