actions - add actual full version to log ?
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 8.9k
- Forks
- 2.8k
- PR merge metrics
- No merged PRs in 30d
Description
Recently had a issue with checking out a ref (tag) on a repo installed/cloned via this action. Something recently broke what previously worked. Not quite sure as to the cause, but I wondered one thing.
Most people pin actions to the major version in workflows. Could actions start logging the full version in the log? It would help when things are acting 'odd'.
I've got a public custom action, with a dist folder, and I just added the following line in js code:
const version = JSON.parse(fs.readFileSync(`${__dirname}\\package.json`, 'utf8')).version
And then logged it.
Building it copied package.json it to the dist folder, but it's a small, and that way the version isn't duplicated...
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the action entry point and its generated dist folder, then inspect the package.json version that is already copied there. Confirm how the action currently logs its version and define done as having the full action version visible in workflow logs when users pin only a major version.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100