Improve Workflows

Assessment

This issue has not been assessed yet.

Description

This issue aims to improve GitHub Action Workflows.

Testing Workflow

Currently, some tests are not executed in the Workflow & cargo make pr-flow (and they are actually broken / does not work if you try to run them).

Related: #2403.

test dom_bundle::btag::tests_without_browser::html_if_bool ... FAILED
test dom_bundle::btag::tests_without_browser::html_if_option ... FAILED

• Properly gate all wasm and non-wasm tests so that cargo test can work & update workflow so that cargo test is run as well.
• Unify how tests are run on both local and CI (by adapting cargo-make?), or remove local-based flow (as pointed out here).

Website and API docs Workflow

If the Website and API docs workflow both meets the condition to be run on a pull request, the latter one will override the comment of the one completed first.

• Give the action a way to differentiate comments of each other (maybe a title?)

Benchmark Workflow

Currently, benchmark result in a comment posted on every commit while a pull request is open and a comment on every merge commit.

1. Only run if the pull request modifies the actual code (packages/* or tools/*)
2. Edit existing comments if one is present
3. Omit the comment on master branch after merging

Size Comparison Workflow

1. Make the comment collapsable
2. Show build system information (version of rust, wasm-bindgen, etc.) and commit ref
3. Show difference in percentage as well
4. Show a summary and warns if any example has received a substantial increase.

Contributor guide

Open the contributing guide

First steps

1. Read the whole issue, then the project's contributing guide.
2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
3. Fork the repository and make your change on a branch.
4. Open a pull request that references the issue number.

More from yewstack/yew

• `NodeRef` documentation is misleading about usage with `use_effect_with` Open
  documentation

  Difficulty 3/5 1-2 days Newbie friendliness 70/100

  yewstack/yew#4226 · Opened Sep 16, 2026

• use_linked_state retries indefinitely after an initial LinkError::Internal Open
  bug

  Difficulty 3/5 1-2 days Newbie friendliness 68/100

  yewstack/yew#4218 · Opened Sep 7, 2026

• Migrate away from unmaintained proc-macro-error crate Open

  Difficulty 5/5 Over a week Newbie friendliness 35/100

  yewstack/yew#4177 · 1 comment · Opened Jun 26, 2026

• Test and simplify more rust code snippets on the website Open
  documentation

  Difficulty 4/5 3-5 days Newbie friendliness 42/100

  yewstack/yew#4134 · 1 comment · Opened Apr 15, 2026

• `for x in children.iter()` works in `html!` but `for x in &children` does not Open

  Difficulty 3/5 1-2 days Newbie friendliness 72/100

  yewstack/yew#4073 · 4 comments · Opened Mar 18, 2026

All issues in yewstack/yew

Similar issues

• [Bug] 줄수 채점이 가로 전환을 안 탄다 — 조판은 72850, 채점은 48190 으로 잰다 Open

  Difficulty 2/5 1-3 hours Newbie friendliness 86/100

  kwakseongjae/auto-hwp#319 · Opened Sep 20, 2026

• rtk ast-grep: a directory named after a subcommand disables filtering for the whole implicit-run invocation Open
  area:cli bug filter-quality good first issue priority:medium

  Difficulty 2/5 1-3 hours Newbie friendliness 84/100

  rtk-ai/rtk#4162 · 1 comment · Opened Sep 20, 2026

• Add comment clarifying the meaning of `InteractionDisabled` Open

  Difficulty 1/5 Under an hour Newbie friendliness 72/100

  bevyengine/bevy#25861 · Opened Sep 20, 2026

• v1 manifest list: existing_files_count is the table-wide total-data-files Open
  comp-datalake

  Difficulty 2/5 1-3 hours Newbie friendliness 88/100

  ClickHouse/ClickHouse#121222 · Opened Sep 20, 2026

• Feature Request: Bold Thread Titles in Codex Remote Open
  enhancement remote

  Difficulty 2/5 1-3 hours Newbie friendliness 68/100

  openai/codex#46828 · Opened Sep 20, 2026

More Rust issues