Ability to add other artifacts to the release commit
See original GitHub issueATM, I’m amending because I want the produced artifacts to be part of the chore(release): x.x.x
commit.
"prerelease": "webpack -p --bail", //produces some bundle artifacts that I want to commit
"release": "standard-version -s",
"postrelease": "git commit -a --amend --no-edit"
However, because of the way git works this creates a new commit object since the original commit is tagged before the amend happens. What would be nice is if my postrelease
script was really a poststandard-version
script (i.e. a “lifecycle-style” hook like the npm run script itself).
Issue Analytics
- State:
- Created 7 years ago
- Reactions:4
- Comments:11 (9 by maintainers)
Top Results From Across the Web
Release artifacts and artifact sources - Azure Pipelines
A release is a collection of artifacts in your DevOps CI/CD processes. An artifact is a deployable component of your application.
Read more >Is it possible to commit artifacts into the git? - GitLab CI/CD
I use the following .gitlab-ci.yml compile_pdf: image: aergus/latex script: - latexmk -pdf test.tex artifacts: paths: - test.pdf W…
Read more >Link Commits and Work Items to Release using GIT
I'm trying to get a list of Commits and Work Items since my previous Release. I'm using a GIT repository and would like...
Read more >How to publish GitHub Actions artifacts by example
Here's a simple example on how a developer can publish GitHub Actions artifacts for download once a build workflow successfully completes.
Read more >Tip 6: Uploading artifacts in a GitHub Actions workflow
We want to save that content as formal build artifacts that we can handoff between various jobs as part of a more sophisticated...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I think that
--commit-all
could potentially work for my usecase. It seems similar to what I’ve done with the built-in version script:Then when npm’s versioning runs, it just commits the entire thing.
Yes, currently the commit-all flag just commits already staged changes. That might seem confusing, but I actually think it allows for greater control over the process. Needs to be clear in the documentation though. I’ll take a look at the pr soon when I’m on my comp.