🦙 TinaCMS Dependency - Pull Request - Show a clear call-to-action after saving additional changes on an existing branch

Requested by: @GordonBeeming via YakShaver.ai 🦬
cc: @GordonBeeming, @Marxoz, @PothieuG, @Freego1783

Hi Team!

  🟥  Watch the video (1 min 18 sec)

  Url from screen share: https://www.ssw.com.au/rules/admin#/rules/use-github-copilot-cli-secure-environment

Pain

When a user saves additional changes to an existing branch in Rules V3 (TinaCMS), there is no obvious or prominent indication of how to return to or edit the related pull request. Unlike the initial edit, which shows a helpful popup with a direct link to the pull request, subsequent saves provide no clear feedback or next-step guidance. This creates confusion and a poor user experience. The system should display a clear, visible call-to-action after saving changes that guides the user to view, edit, or continue working on the pull request.

Acceptance Criteria

1. After saving changes to an existing branch, the user is shown a clear and visible confirmation message.
2. The confirmation message includes an explicit call-to-action (e.g., a button or link) to view or edit the associated pull request.
3. The call-to-action is visually prominent and consistent with the initial branch creation experience.
4. The user does not need to guess or explore unrelated UI elements to find the pull request.
5. The behavior is consistent across Rules V3 (TinaCMS) editing workflows.

Screenshot

Figure: Missing prompt to navigate to pull request after saving changes

Start with the Rules V3 (TinaCMS) existing-branch save flow and compare it with the initial branch creation experience described in the issue and screenshot. Done means saving additional changes shows a prominent confirmation with a link or button to view or edit the associated pull request consistently across Rules V3 editing workflows.