Back to the dashboard

Signed-in check

These are the things only you can try, because they need your GitHub sign-in. Work through them in order. Mark each one Worked or Problem, add a note for a problem, then copy your results and send them back. Your answers stay in this browser.

Loading...

Signing in and out

  1. Do: Click the Sign out icon in the sidebar (below Settings; at the right end of the top bar on a phone).

    Expect: You land on the sign-in page.

  2. Do: Click Sign in with GitHub and approve if GitHub asks.

    Expect: You come back to your dashboard with your repos, no error message. GitHub remembers you, so it may go straight back without asking. That is normal: mark it Worked.

The dashboard on real data

  1. Do: Pick three repos and compare each card's percentage with GitHub (closed issues divided by all issues).

    Expect: They match. A repo with no milestones counts all its issues.

  2. Do: Look at the focus card, the milestone progress card and the Today list.

    Expect: They are about the same project, and the Today tasks link to real open issues.

Stars, focus and types

  1. Do: Star a project, move it up and down, then unstar it.

    Expect: It appears under High priority, the order changes, and it all survives a reload.

  2. Do: Make focus on a backlog project. Type a reason shorter than 5 characters first, then a real one.

    Expect: The short reason is refused. The real one switches focus, the old project becomes paused, and the Focus log card shows your reason.

    This changes your real focus. Switch back afterwards with the reason “testing”.

  3. Do: Change a project's type to Practice, then back to Project.

    Expect: It moves to Practice and school, loses its star and focus buttons, and comes back.

Finishing a project

  1. Do: On a spare project, choose Mark project finished, pick Finished, set a date that is not in the future, and confirm.

    Expect: It moves to Finished and deployed with that date. A future date is refused.

    Use a project you do not mind changing. Reopen it afterwards.

  2. Do: Click Change date, then Reopen.

    Expect: The date changes. Reopen puts it back in the backlog.

  3. Do: Mark another spare project as Deployed with an address that is not http or https, then with a real one.

    Expect: The wrong address is refused. The real one is saved and shows Visit site.

    Reopen it afterwards.

Away mode, settings and the checklist

  1. Do: Click Going away? and set a return date, then clear it.

    Expect: The stalled alert pauses until that date, and comes back when you clear it.

  2. Do: Open Settings, change the stalled days, save, reload, then put it back.

    Expect: It says saved, the new value is there after the reload, and the old one returns.

  3. Do: In the definition of done card, add an item, tick it, then remove it.

    Expect: Each change stays after a reload. It never blocks Mark project finished.

GitHub Projects

  1. Do: Add a task: type a title, read the preview, then confirm.

    Expect: An issue appears on GitHub in the Project, and the issue count goes up by one.

    It creates a real issue. Close it on GitHub afterwards.

  2. Do: Add a milestone with a title and no date, then read the preview and confirm.

    Expect: The milestone exists on GitHub.

    It creates a real milestone. Close it on GitHub afterwards.

  3. Do: Open Check sync. If it says some edits are ignored, expand Show the ignored edits.

    Expect: The message makes sense and the card shows a pill with the answer. If edits are ignored they are listed by name; if the dialog lists none, there is nothing to expand, so mark it Worked.

  4. Do: On a spare repo that is connected to a Project, click Add the rules to this repo, read the text, and open the pull request.

    Expect: One pull request on GitHub that changes only CLAUDE.md. Nothing is merged for you.

    Close the pull request if you do not want the rules.

  5. Do: Click Look for duplicate issues.

    Expect: Each listed issue really does repeat the one named beside it. Close only those you are sure about.

    Closing marks them not planned. You can reopen any of them on GitHub.

The daily jobs

  1. Do: In Vercel, open the project, then Settings, then Cron Jobs, and press Run on the snapshot and the daily email.

    Expect: Both finish with a success. The email arrives with the right greeting and today's tasks. Scheduled times are in UTC, and on the free plan a job may run any time within its hour. If no email comes, open Logs in Vercel, find /api/cron/daily-email, and write down the response: it says skipped and why (Away mode, reminder off, or no focus project).