Change .gitignore for VS Code #13836
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
Allow workspace files like settins.json or extensions.json to be checked in by updating .gitignore file. See jhipster#13715
egvimo
force-pushed
the
feature/gitignore-vscode
branch
from
424d687
to
7dd12ed
Compare
atomfrede
approved these changes
Feb 16, 2021
1 task
coderguy-tech
pushed a commit
to coderguy-tech/generator-jhipster
that referenced
this pull request
Jun 1, 2021
Allow workspace files like settins.json or extensions.json to be checked in by updating .gitignore file. See jhipster#13715
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Change
.gitignorefile to allow certain VS Code workspace files.See #13715
Please make sure the below checklist is followed for Pull Requests.
When you are still working on the PR, consider converting it to Draft (bellow reviewers) and adding
skip-cilabel, you can still see CI build result at your branch.