redhat-developer / redhat-developer/vscode-xml
Package information into .vsix builds in order to identify commit/build
Open
Nobody has claimed this yet.
build
debt
- Dominant language
- TypeScript
- Stars
- 328
- Forks
- 101
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 7
Description
Package something like git commit id or Jenkins build id in order to be able to reproduce issues in broken builds of vscode-xml.
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 .vsix packaging entry point and the Jenkins build configuration for vscode-xml. Determine which commit or build identifier is available there, then verify that a produced .vsix contains it so issues from broken builds can be traced back to the source build.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, typescript, vscode
- Domain
- build-system, release
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100