From f88a8031be25af8640df8763b128be4f9937b9b2 Mon Sep 17 00:00:00 2001 From: Nikhil Benesch Date: Fri, 19 Feb 2021 14:20:01 -0500 Subject: [PATCH 1/2] Follow header Title Case convention in mdbook This is to test the new CI workflows. --- mdbook/src/chapter_5/chapter_5_2.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/mdbook/src/chapter_5/chapter_5_2.md b/mdbook/src/chapter_5/chapter_5_2.md index 5ac6fe55c..90599e6f3 100644 --- a/mdbook/src/chapter_5/chapter_5_2.md +++ b/mdbook/src/chapter_5/chapter_5_2.md @@ -14,7 +14,7 @@ Timely dataflow computations are structured so that to send a timestamped messag Before we get into these two aspects, we will first need to be able to name parts of our dataflow graph. -## Dataflow structure +## Dataflow Structure A dataflow graph hosts some number of operators. For progress tracking, these operators are simply identified by their index. Each operator has some number of *input ports*, and some number of *output ports*. The dataflow operators are connected by connecting each input port to a single output port (typically of another operator). Each output port may be connected to multiple distinct input ports (a message produced at an output port is to be delivered to all attached input ports). From 495d81f7f010e29a29158112175721b16a5f025a Mon Sep 17 00:00:00 2001 From: Nikhil Benesch Date: Fri, 19 Feb 2021 14:23:47 -0500 Subject: [PATCH 2/2] Check out code in deploy flow --- .github/workflows/deploy.yml | 1 + 1 file changed, 1 insertion(+) diff --git a/.github/workflows/deploy.yml b/.github/workflows/deploy.yml index 69010e3df..ccb07f589 100644 --- a/.github/workflows/deploy.yml +++ b/.github/workflows/deploy.yml @@ -9,6 +9,7 @@ jobs: deploy: runs-on: ubuntu-20.04 steps: + - uses: actions/checkout@v2 - run: cargo install mdbook --version 0.4.6 - run: cd mdbook && mdbook build - uses: JamesIves/github-pages-deploy-action@4.0.0