Investigate how to decouple code web stable and insiders configuration
Open
Nobody has claimed this yet.
editor: code (browser)
meta: never-stale
team: IDE
type: improvement
- Dominant language
- TypeScript
- Stars
- 13.8k
- Forks
- 1.4k
- Avg merge
- 17h 58m
- Merged PRs (30d)
- 5
Description
We need to investigate possible ways of decoupling code web stable and insiders config, it gets a bit cumbersome when we want to release a new code stable image, and we have modified the dockerfile (e.g. due to new upstream changes related to the server) since the last stable release and this changes are not backwards compatible
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 examining the Dockerfile and the configuration used for code web stable and insiders images. Trace how a new stable image is released when upstream server changes have altered the Dockerfile. Done means documenting or implementing a decoupling approach that avoids incompatible changes affecting the stable release.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dockerfile
- Domain
- devops, release
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100