Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • P poky
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Terraform modules
    • Model experiments
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • automation
  • so
  • mirror
  • poky
  • Repository
  • poky
  • .gitignore
Find file Blame History Permalink
  • Adrian Freihofer's avatar
    vscode: drop .vscode folder · a510d455
    Adrian Freihofer authored Feb 15, 2024
    There is a new official bitbake plugin:
    https://marketplace.visualstudio.com/items?itemName=yocto-project.yocto-bitbake
    
    This plugin automatically updates the .vscode/settings.json file.
    Having the settings.json file in git and a plugin which modifies this
    file is not ideal. It can lead to anoying situations especially when
    working with git. For example a git stash reverts the settings which are
    automatically applied by the plugin. While git stashed the settings.json
    file the plugin immediately changes the file again and tries to run
    bitbake based on the newly generated settings. When git does a stash pop
    the restored settings.json file conflicts with the new settigns.json
    file which has been generated while the git stash took place.
    
    Therefore this patch removes the .vscode folder from git.
    
    Removing the settings.json leads to other issues as already described
    in the commit message of 5ff688fe. But we still need another solution
    where the settings.json file is not in Git.
    
    Discussion is here:
    https://github.com/yoctoproject/vscode-bitbake/issues/95
    
    
    
    (From OE-Core rev: f36771e155b9e0cf24a885bf3340d59036aa42c5)
    
    Signed-off-by: default avatarAdrian Freihofer <adrian.freihofer@siemens.com>
    Signed-off-by: default avatarRichard Purdie <richard.purdie@linuxfoundation.org>
    a510d455