sillsdev / sillsdev/languageforge-lexbox
set content type on msix bundle when uploading as a release asset
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 9
- Forks
- 8
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 49
Description
Describe the feature
Right now we're using a github action to create new releases and upload the release assets. We want the msixbundle to have the content type application/msixbundle
The docs here, indicate that we can tell github what content type to use by setting a Content-Type header when uploading the file.
The workflow that needs to change is
https://github.com/sillsdev/languageforge-lexbox/blob/53ec30e195984d9dcd2b3a07b0d8a1a122ca3ec0/.github/workflows/fw-lite.yaml#L310-L321
we're using the softprops/action-gh-release action to generate the release, in their docs, they output the upload URL which we can use the upload to. So we would want to modify our current release and remove the bundle file from the current action and upload it in a follow up step.
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 with .github/workflows/fw-lite.yaml lines 310-321, then read the softprops/action-gh-release output documentation and GitHub's release asset upload documentation linked in the issue. Remove the MSIX bundle from the current release action and upload it in a follow-up step using the upload URL with Content-Type set to application/msixbundle.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, yaml
- Domain
- ci-cd, release
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100