rfc-editor-drafts / rfc-editor-drafts/base-devcontainer
a gitignore file for the base-devcontainer
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 2
- Forks
- 0
- Avg merge
- 19m
- Merged PRs (30d)
- 1
Description
Currently the editors are creating their own .gitignore files to capture devcontainer-lock.json. It's been suggested that this file could be listed in a system-wide .gitignore. Could this be added to the container configuration?
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 inspecting the base-devcontainer configuration and how the image sets system-wide development settings. Check how devcontainer-lock.json is handled and confirm the appropriate ignore configuration location. Done means the base container provides a system-wide ignore entry so editors no longer need to create their own .gitignore files.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dockerfile
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 72/100