SSWConsulting / SSWConsulting/SSW.Rules

🐛 Bug - Show co-author instead of TinaCloud bot as last updated author

Open
#2,706 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Requested by: @brookjeynes-ssw via YakShaver.ai 🦬
cc: @brookjeynes-ssw, @wicksipedia, @BenDunkerleySSW, @Marxoz, @PothieuG, @Freego1783

Hi Team!

  🟥  Watch the video (1 min 34 sec)

Pain

In Rules V3 (TinaCMS), the rule details page incorrectly displays the "TinaCloud" bot as the last updated author when a commit contains a co-author. The UI should detect when the commit author is the TinaCloud app/bot and instead extract and display the human co-author from the commit message/history.

Acceptance Criteria
  1. When the latest commit author is the TinaCloud bot and the commit contains a co-author, the UI displays the human co-author as the last updated author.
  2. The system parses commit metadata or commit messages to identify co-authored-by entries.
  3. If no co-author exists, the TinaCloud bot continues to display as the author.
  4. The author displayed on the rule page matches the expected human contributor from the commit history.
  5. Existing author rendering behavior for non-TinaCloud commits is unchanged.
Reproduce Steps
  1. Open a rule in Rules V3 (TinaCMS) where the latest commit was authored by the TinaCloud bot with a co-author.
  2. Observe the "Last Updated By" section on the rule page.
  3. Open the Git history for the same rule.
  4. Verify that the commit contains both the TinaCloud bot and a human co-author.
  5. Notice that the UI only displays the TinaCloud bot instead of the human contributor.
Screenshot

Screenshot
Figure: TinaCloud bot shown instead of actual last author

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

Start at the Rules V3 rule details page and locate the "Last Updated By" rendering. Inspect the latest commit metadata and message for co-authored-by entries, then verify the display against Git history for both TinaCloud commits with and without a co-author, while preserving non-TinaCloud behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
nextjs, typescript
Domain
frontend, web-dev
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
65/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.