MarketSquare / MarketSquare/SSHLibrary
Create devcontainer for development and debugging
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 167
- Forks
- 145
- PR merge metrics
- No merged PRs in 30d
Description
If we have a devcontainer, contributors would not need to recreate the test workflow conditions locally.
- devcontainer added to repo
- devcontainer can be used out-of-box in VSCode
- test cases can be executed in VSCode (devcontainer)
Hint: there is a dockerfile in atest folder. Maybe we can reuse it (and combine it with ci-yml workflow)
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 reviewing the Dockerfile in the atest folder and the CI workflow to understand the existing test conditions. Define the devcontainer so it works out of the box in VS Code and allows the test cases to run there. Done means the devcontainer is committed and all listed workflow checks pass inside it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, python, vscode
- Domain
- developer-experience, devops, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100