JoshuaKGoldberg / JoshuaKGoldberg/create-typescript-app

🛠 Tooling: Investigate simplifying release commenter version name

Open
#1,115 4 comments 0 reactions 0 assignees View on GitHub
area: tooling status: accepting prs
Dominant language
TypeScript
Stars
1.4k
Forks
89
Avg merge
1m
Merged PRs (30d)
3

Description

### Bug Report Checklist

- [X] I have tried restarting my IDE and the issue persists.
- [X] I have pulled the latest `main` branch of the repository.
- [X] I have [searched for related issues](https://github.com/JoshuaKGoldberg/create-typescript-app/issues?q=is%3Aissue) and found none that matched my issue.

### Overview

Following #427 -> #428: per https://github.com/apexskier/github-release-commenter/issues/432, it looks like `${{ payload.release.tag_name }}` should be usable to get the tag name of the released version. It'd be nice to use that instead of having to manually `run` a command: https://github.com/JoshuaKGoldberg/create-typescript-app/blob/d53c4eea73e084307a2d5eb9386727d0e3bf91ac/.github/workflows/post-release.yml#L8

Investigation required. If this strategy does work, hooray! Accepting PRs!

### Additional Info

_No response_

Contributor guide

Open the contributing guide

Research direction

Start with .github/workflows/post-release.yml at the linked line and compare its current version-name command with the GitHub Actions payload.release.tag_name expression. Read the referenced github-release-commenter issue to verify whether the expression is supported. Done means the release commenter uses the released tag directly and the workflow completes with the expected version name.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions
Domain
ci-cd, release
Issue type
Refactor
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.