Where does it put artifacts?
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 134
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
I'm using this in conjunction with [semantic-release](https://semantic-release.gitbook.io/semantic-release/) and I'd like to upload the firefox xpi/chrome zip file to the corresponding GitHub release at the end of the build, but it's not clear to me where those files end up.
Contributor guide
No contributing guide indexed for this repository
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 where wext-shipit creates the Firefox XPI and Chrome ZIP artifacts, then verify their output paths. Document those paths and confirm how they can be supplied to semantic-release for upload to the corresponding GitHub release.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, javascript
- Domain
- release
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100