• Mayank Mittal's avatar
    Moves `launch.json` to template file in `.vscode/tools` (#55) · d0310cda
    Mayank Mittal authored
    # Description
    
    The `launch.json` file is very user-specific. Previously this was always
    getting pushed along with other commits which led to merge conflicts
    when merging branches from different users.
    
    Now, the `launch.json` is generated from a template if it doesn't
    already exist in the `.vscode` directory. The users can modify the
    `.vscode/launch.json` as they please afterward, but their changes won't
    get pushed to git itself.
    
    Fixes #46
    
    ## Type of change
    
    <!-- As you go through the list, delete the ones that are not
    applicable. -->
    
    - Bug fix (non-breaking change which fixes an issue)
    
    ## Checklist
    
    - [x] I have run the [`pre-commit` checks](https://pre-commit.com/) with
    `./orbit.sh --format`
    - [ ] I have made corresponding changes to the documentation
    - [x] My changes generate no new warnings
    - [ ] I have added tests that prove my fix is effective or that my
    feature works
    - [ ] I have updated the changelog and the corresponding version in the
    extension's `config/extension.toml` file
    d0310cda
Name
Last commit
Last update
.github Loading commit data...
.vscode Loading commit data...
docker Loading commit data...
docs Loading commit data...
source Loading commit data...
.dockerignore Loading commit data...
.flake8 Loading commit data...
.gitignore Loading commit data...
.pre-commit-config.yaml Loading commit data...
LICENSE Loading commit data...
README.md Loading commit data...
VERSION Loading commit data...
orbit.sh Loading commit data...
pyproject.toml Loading commit data...