ci: Add git-town workflow to display PR stack visualization#5577
ci: Add git-town workflow to display PR stack visualization#5577ericapisani wants to merge 2 commits intomasterfrom
Conversation
Add a GitHub Actions workflow that uses git-town/action to automatically render the stacked pull request visualization in PR descriptions. The workflow runs on pull_request events and updates the <!-- branch-stack --> marker in the PR template. Also add the branch-stack placeholder to the PR template so git-town knows where to inject the visualization. Co-Authored-By: Claude <noreply@anthropic.com>
Semver Impact of This PR🟢 Patch (bug fixes) 📋 Changelog PreviewThis is how your changes will appear in the changelog. Internal Changes 🔧
🤖 This preview updates automatically when you update the PR. |
Codecov Results 📊✅ 134 passed | Total: 134 | Pass Rate: 100% | Execution Time: 21.50s 📊 Comparison with Base Branch
All tests are passing successfully. ✅ Patch coverage is 100.00%. Project has 13215 uncovered lines. Coverage diff@@ Coverage Diff @@
## main #PR +/-##
==========================================
+ Coverage 28.02% 33.59% +5.57%
==========================================
Files 189 189 —
Lines 19899 19899 —
Branches 6460 6460 —
==========================================
+ Hits 5575 6684 +1109
- Misses 14324 13215 -1109
- Partials 525 659 +134Generated by Codecov Action |
|
Closing this as there's an underlying issue within git-town that prevents our use of it within this repository. Specifically, if a user were to open a pull request from a forked repository that is from a |
Add a GitHub Actions workflow that uses
git-town/actionto automatically render the stacked pull request visualization in PR descriptions.When a PR is opened, reopened, or pushed to, the workflow injects the branch stack into the
<!-- branch-stack -->marker in the PR template. This makes it easy to see the full stack context without leaving the PR page.The PR template is updated to include the marker and a "Pull request stack" section where the visualization will appear — always below the user-provided description.
The workflow follows existing repo security conventions: both actions are pinned to full commit SHAs, permissions are deny-all at the workflow level with only
contents: readandpull-requests: writegranted at the job level, andfetch-depth: 0is set so git-town has the full history needed to compute the stack.