Skip to content

ci(screenshot): screenshot generation#12

Merged
FLchs merged 10 commits into
masterfrom
feat/separate-screenshot-action
Mar 9, 2026
Merged

ci(screenshot): screenshot generation#12
FLchs merged 10 commits into
masterfrom
feat/separate-screenshot-action

Conversation

@FLchs
Copy link
Copy Markdown
Owner

@FLchs FLchs commented Mar 9, 2026

  • Create new generate-screenshot.yml workflow
  • Remove screenshot job from auto-release.yml
  • Allow manual trigger and weekly scheduled runs

FLchs added 5 commits March 9, 2026 10:46
- Create new generate-screenshot.yml workflow
- Remove screenshot job from auto-release.yml
- Allow manual trigger and weekly scheduled runs
- Run screenshot workflow on pushes to feat/separate-screenshot-action branch
- Change 'bunx run preview' to 'bun run preview' to correctly run npm script
- Update pkill to search for 'vite' instead of 'serve'
- Change viewport size to 672x1193px
- Increase wait timeout to 30 seconds
@FLchs FLchs force-pushed the feat/separate-screenshot-action branch from 81822f4 to cea64e6 Compare March 9, 2026 09:47
Screenshot bot and others added 5 commits March 9, 2026 09:48
- Add id to server-card-content element for targeting
- Set viewport to 1024x900px (Tailwind lg breakpoint)
- Use element selector to screenshot only card content
- Keep 30 second wait timeout
- Add tsx dependency for running TypeScript scripts
- Create take-screenshot.ts script to screenshot specific element
- Update workflow to use script instead of CLI command
- Screenshot #server-card-content element only
- Run screenshot workflow on push to master instead of feat branch
- Push screenshot to isolated 'screenshot' branch to avoid polluting main
- Update README to reference screenshot from screenshot branch
- Remove weekly schedule trigger
@FLchs FLchs merged commit cc113e6 into master Mar 9, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant