SSWConsulting / SSWConsulting/SSW.Rules

🦙 Bug - TinaCMS Dependency - Branch list shows indexing failed and missing editor details

Open
#2,415 0 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

TinaCMS YakShaver
Dominant language
TypeScript
Stars
26
Forks
17
Avg merge
14h 39m
Merged PRs (30d)
2

Description

Requested by: @kikibianc via YakShaver.ai 🦬
cc: @kikibianc, @0xharkirat, @brookjeynes-ssw, @wicksipedia, @tiagov8, @Marxoz, @PothieuG, @Freego1783

Hi Team!

  🟥  Watch the video (1 min 5 sec)

  Url from screen share: https://www.ssw.com.au/rules/admin/#/rules/educate-your-developer

Pain

When editing a rule in Rules V3 (TinaCMS), selecting the main branch in the branch list briefly loads and then displays an "indexing failed" message for two branches. These branches are over a month old and should not be failing. Additionally, the branch list does not show who last edited the branches, and there is no direct link to identify or navigate to the editor or branch details.

Acceptance Criteria
  1. Branch list does not display "indexing failed" for valid branches.
  2. Any genuine indexing failure includes a clear, actionable error message.
  3. Each branch displays the name of the user who last edited it.
  4. Each branch includes a clickable link to view branch details or the associated editor.
  5. Loading the main branch completes successfully without transient errors.
Reproduce Steps
  1. Navigate to Rules V3 (TinaCMS).
  2. Open an existing rule for editing.
  3. Open the branch list.
  4. Click on the main branch.
  5. Observe the loading behavior and the "indexing failed" message for some branches.
  6. Note the absence of editor information and links for the affected branches.
Screenshot

Screenshot
Figure: Branch list shows indexing failed for two branches with missing editor information

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

Reproduce the issue in Rules V3 by opening an existing rule, opening the branch list, and selecting the main branch. Trace the TinaCMS branch-list integration from that entry point; done means valid branches load without transient indexing errors, genuine failures are actionable, and each branch shows its last editor with a details or editor link.

Written by the indexing model from the issue text.

Assessment

Tech stack
nextjs, typescript
Domain
frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.