( the primaryDescriptionMarkdown is long - several lines, include images, as long as you want )

In this course we <headline of what we do>. <why this technology is good> but <here's how learning it is problem>. 

In <the length of these lessons> we cover <three salient points about what we cover. Your BEST points>. Its <however long it is> and comes with <these bonus features, and reasons to buy. code, etc.>

It's taught by <author name> who <credibility, reason you should listen to them>. <social proof, if you have it yet>

<then you can list other supporting stuff you want to add, anything you want here>

-------
Example:
-------

We created a free course to create your first GraphQL server (from scratch) using Node and TypeScript. TypeScript and GraphQL are a powerful combo, but there's a lot of confusing edges if you're getting it setup the first time.

In this course we cover the basics of getting TypeScript setup with Node, how GraphQL works, and how to set up a GraphQL server using Apollo server. It's two hours long, it comes with complete code examples, and we walk through the code step-by-step.

It's taught by my friend, Shopify-engineer Hassan Djirdeh and he's integrated what he's learned using GraphQL in production as an engineer at Shopify. We've already had over 1,300 students enroll and it's been getting great reviews so far.

// ... and so on

In this course we <headline of what we do>. <why this technology is good> but <here's how learning it is problem>. 

( the summary is short - one or two lines )

Bundling and Automation in Monorepos

---
title: CI concurrency and push triggers
privateVideoUrl: https://stream.mux.com/7IXrkHh5DPZ3AhhUX6HaQ301Vwfom023RIFu01lFPV02i7E.m3u8
isPublicLesson: false
originalCode: https://github.com/VanTanev/monorepo/tree/279dc6201799239b8b8d26a0a023ca7ccdd4219f
code: https://gitlab.com/fullstackio/books/newline-course-apps/ivan-tanev-monorepo-automation-app/-/tree/main/course_code/module_05
---

# CI concurrency and push triggers

In the previous lesson, we added a basic CI workflow.

In this lesson, we'll make two improvements that matter immediately in real repos:

1.  Run CI on `push` as well as `pull_request`.
2.  Add workflow concurrency so GitHub cancels stale runs when new commits arrive.

These are small changes, but they improve both correctness and CI ergonomics.

## Run CI on push

Our initial workflow only ran on pull requests, so our main branch never ran CI.

To fix that, we add a `push` trigger.

We scope it to the default branch so we don't run CI for every push to every branch twice (once for `push`, once for `pull_request`).

**.github/workflows/ci.yaml (snippet)**

```yaml
on:
  pull_request:
  push:
    branches:
      - "main"
```

Now CI runs:

-   on pull requests
-   on merges to `main`

## Add concurrency (cancel stale runs)