Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

✨ add a demo-update generation workflow step to let us know when we have broken demo generation #444

Merged
merged 1 commit into from
Oct 29, 2024
Merged

✨ add a demo-update generation workflow step to let us know when we have broken demo generation #444

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 22 additions & 0 deletions .github/workflows/demo.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,22 @@
name: demo

on:
workflow_dispatch:
merge_group:
pull_request:
push:
branches:
- main
Comment on lines +3 to +9
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@LalatenduMohanty to your question - this section describes when the workflow will be triggered.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry, I read the question wrong. Yes, this is limited in scope to PRs pushing to main branch. (But folks can manually run the make target in their local to test.)


jobs:
demo:
runs-on: ubuntu-latest
env:
TERM: linux
steps:
- run: sudo apt update && sudo apt install -y asciinema curl
- uses: actions/checkout@v4
- uses: actions/setup-go@v5
with:
go-version-file: "go.mod"
- run: make demo-update