Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

"re-check CI" is a span, and its busy state is colour-only

Open Beginner friendly
#158 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

  • #201 by @yff124 — closed without merging

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
88/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
javascript, react

Research direction

In website/src/ui.jsx, search for act("ci") in the PR status line; then read the nearby component and the related cases in website/test/clickableContent.test.mjs. Update the control and add a test asserting it is a button. Done means it is disabled while busy, keeps its existing appearance, and shows “Checking CI…”; run cd website && npm test.

Written by the indexing model from the issue text.

Description

accessibility good first issue

In the PR status line, "re-check CI" is <Box component="span" onClick={() => !busy && act("ci")}>. It cannot be focused, and while it is busy the only hint is a colour change.

Where: website/src/ui.jsx. Search for act("ci").

Done when it is a <button type="button"> (or Link component="button") with disabled={!!busy}, styled to look the same. While busy, the label reads "Checking CI…".

Test: add a case to website/test/clickableContent.test.mjs (or a new *.test.mjs beside it) asserting the element is now a button.


Getting started: pip install -e ".[dev]", then python -m pytest -q (offline). UI work: cd website && npm ci && npm test (Node 22). See CONTRIBUTING.md. One small PR with the change (and its test, where there is one) is perfect.

Dominant language
Python
Stars
116
Forks
22
Avg merge
13h 21m
Merged PRs (30d)
53

Getting set up

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 ldbumble/taskuary

All issues in ldbumble/taskuary

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.