The-Homebrew-Cloud/N64FlashcartMenu
2
0
Fork 0
mirror of https://github.com/Polprzewodnikowy/N64FlashcartMenu.git synced 2025-01-24 07:41:14 +01:00
Code Issues Packages Projects Releases Wiki Activity
N64FlashcartMenu/.devcontainer/devcontainer.json

28 lines
761 B
JSON
Raw Normal View History

Add dev container.
2023-02-26 23:14:51 +00:00
{
Improve devcontainer Co-Authored-By: Mateusz Faderewski <kontakt@mateuszfaderewski.pl>
2023-04-01 00:58:59 +01:00
"name": "N64FlashcartMenu",
"build": {
"dockerfile": "Dockerfile"
},
Minor improvements
2023-02-27 00:48:22 +00:00
"mounts": [
Remove tests from dev container
2023-02-28 17:39:39 +00:00
"source=n64flashcartmenu-bashhistory,target=/commandhistory,type=volume"
Minor improvements
2023-02-27 00:48:22 +00:00
],
Browser rewrite / Boot bug fixes
2023-07-02 21:52:58 +02:00
"postCreateCommand": "git submodule update --init && cd ./libdragon && ./build.sh",
Minor improvements
2023-02-27 00:48:22 +00:00
"customizations": {
"vscode": {
"extensions": [
Improve devcontainer Co-Authored-By: Mateusz Faderewski <kontakt@mateuszfaderewski.pl>
2023-04-01 00:58:59 +01:00
"ms-vscode.cpptools",
Remove un-necessary extensions
2023-05-28 21:09:19 +00:00
"ms-vscode.makefile-tools"
Improve devcontainer Co-Authored-By: Mateusz Faderewski <kontakt@mateuszfaderewski.pl>
2023-04-01 00:58:59 +01:00
],
"settings": {
"git.ignoredRepositories": [
Changed config library from toml to mini.c toml library didn't offer any way to serialize config file
2023-07-11 18:00:18 +02:00
"libdragon",
Suppress dirty submodules in VSCode (#38) <!--- Provide a general summary of your changes in the Title above --> ## Description <!--- Describe your changes in detail --> When running in a dev container, certain submodules show changes in VSCode. GitHub Desktop does not show them. This PR also adds missing Submodules to the devcontainer.json git.ignoredRepositories. ## Motivation and Context <!--- What does this sample do? What problem does it solve? --> <!--- If it fixes/closes/resolves an open issue, please link to the issue here --> Speculative fix. If there is a better way, it is welcome! ## How Has This Been Tested? <!-- (if applicable) --> <!--- Please describe in detail how you tested your sample/changes. --> <!--- Include details of your testing environment, and the tests you ran to --> <!--- see how your change affects other areas of the code, etc. --> ## Screenshots <!-- (if appropriate): --> ## Types of changes <!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: --> - [ ] Improvement (non-breaking change that adds a new feature) - [ ] Bug fix (fixes an issue) - [ ] Breaking change (breaking change) - [x] Config and build (change in the configuration and build system, has no impact on code or features) ## Checklist: <!--- Go over all the following points, and put an `x` in all the boxes that apply. --> <!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [ ] My code follows the code style of this project. - [ ] My change requires a change to the documentation. - [ ] I have updated the documentation accordingly. - [ ] I have added tests to cover my changes. - [ ] All new and existing tests passed. <!--- It would be nice if you could sign off your contribution by replacing the name with your GitHub user name and GitHub email contact. --> Signed-off-by: GITHUB_USER <GITHUB_USER_EMAIL>
2023-08-09 19:49:10 +01:00
"src/libs/libspng",
Changed config library from toml to mini.c toml library didn't offer any way to serialize config file
2023-07-11 18:00:18 +02:00
"src/libs/mini.c",
Suppress dirty submodules in VSCode (#38) <!--- Provide a general summary of your changes in the Title above --> ## Description <!--- Describe your changes in detail --> When running in a dev container, certain submodules show changes in VSCode. GitHub Desktop does not show them. This PR also adds missing Submodules to the devcontainer.json git.ignoredRepositories. ## Motivation and Context <!--- What does this sample do? What problem does it solve? --> <!--- If it fixes/closes/resolves an open issue, please link to the issue here --> Speculative fix. If there is a better way, it is welcome! ## How Has This Been Tested? <!-- (if applicable) --> <!--- Please describe in detail how you tested your sample/changes. --> <!--- Include details of your testing environment, and the tests you ran to --> <!--- see how your change affects other areas of the code, etc. --> ## Screenshots <!-- (if appropriate): --> ## Types of changes <!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: --> - [ ] Improvement (non-breaking change that adds a new feature) - [ ] Bug fix (fixes an issue) - [ ] Breaking change (breaking change) - [x] Config and build (change in the configuration and build system, has no impact on code or features) ## Checklist: <!--- Go over all the following points, and put an `x` in all the boxes that apply. --> <!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [ ] My code follows the code style of this project. - [ ] My change requires a change to the documentation. - [ ] I have updated the documentation accordingly. - [ ] I have added tests to cover my changes. - [ ] All new and existing tests passed. <!--- It would be nice if you could sign off your contribution by replacing the name with your GitHub user name and GitHub email contact. --> Signed-off-by: GITHUB_USER <GITHUB_USER_EMAIL>
2023-08-09 19:49:10 +01:00
"src/libs/minimp3",
Fix ignored lib directory (#40) <!--- Provide a general summary of your changes in the Title above --> ## Description <!--- Describe your changes in detail --> `miniz` directory was incorrectly named `miniz.c` ## Motivation and Context <!--- What does this sample do? What problem does it solve? --> <!--- If it fixes/closes/resolves an open issue, please link to the issue here --> It was not correctly ignored. ## How Has This Been Tested? <!-- (if applicable) --> <!--- Please describe in detail how you tested your sample/changes. --> <!--- Include details of your testing environment, and the tests you ran to --> <!--- see how your change affects other areas of the code, etc. --> ## Screenshots <!-- (if appropriate): --> ## Types of changes <!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: --> - [ ] Improvement (non-breaking change that adds a new feature) - [ ] Bug fix (fixes an issue) - [ ] Breaking change (breaking change) - [x] Config and build (change in the configuration and build system, has no impact on code or features) ## Checklist: <!--- Go over all the following points, and put an `x` in all the boxes that apply. --> <!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [ ] My code follows the code style of this project. - [ ] My change requires a change to the documentation. - [ ] I have updated the documentation accordingly. - [ ] I have added tests to cover my changes. - [ ] All new and existing tests passed. <!--- It would be nice if you could sign off your contribution by replacing the name with your GitHub user name and GitHub email contact. --> Signed-off-by: GITHUB_USER <GITHUB_USER_EMAIL>
2023-08-17 21:14:22 +01:00
"src/libs/miniz"
Improve devcontainer Co-Authored-By: Mateusz Faderewski <kontakt@mateuszfaderewski.pl>
2023-04-01 00:58:59 +01:00
]
}
Minor improvements
2023-02-27 00:48:22 +00:00
}
}
Add dev container.
2023-02-26 23:14:51 +00:00
}
Reference in New Issue Copy Permalink