redhat-developer / redhat-developer/vscode-java
New releases should be automatically git-tagged
Open
Nobody has claimed this yet.
build/infra
- Dominant language
- TypeScript
- Stars
- 2.3k
- Forks
- 546
- Avg merge
- 20h 1m
- Merged PRs (30d)
- 11
Description
The Jenkins build should automatically tag the releases, once the vsix is published to the VSCode Marketplace
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
The issue identifies the Jenkins build and VSCode Marketplace publication as the relevant release entry points, but names no files or tests. Start by locating the Jenkins release job and its VSIX publishing step, then determine how a git tag can be verified after publication. Done means each new Marketplace release is automatically accompanied by the expected git tag.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- ci-cd, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100