Should the .gitignore include an entry for .vscode when using Git and VSCodeIgnore Lightning Application with...
Is there any relevance to Thor getting his hair cut other than comedic value?
What type of postprocessing gives the effect of people standing out
Compare four integers, return word based on maximum
What can I substitute for soda pop in a sweet pork recipe?
Magento 2: Override XML file from vendor folder to app folder doesn't work/update
Why does Starman/Roadster have radial acceleration?
If a druid in Wild Shape swallows a creature whole, then turns back to her normal form, what happens?
When was drinking water recognized as crucial in marathon running?
What if I store 10TB on azure servers and then keep the vm powered off?
How to kill a localhost:8080
Where was Karl Mordo in Infinity War?
Is there a low-level alternative to Animate Objects?
What is a term for a function that when called repeatedly, has the same effect as calling once?
Hacker Rank: Array left rotation
I encountered my boss during an on-site interview at another company. Should I bring it up when seeing him next time?
Why does the 31P{1H} NMR spectrum of cis-[Mo(CO)2(dppe)2] show two signals?
How can I handle a player who pre-plans arguments about my rulings on RAW?
A "strange" unit radio astronomy
Are small insurances worth it
Did Amazon pay $0 in taxes last year?
How do I construct an nxn matrix?
How to count occurrences of Friday 13th
chrony vs. systemd-timesyncd – What are the differences and use cases as NTP clients?
CBP Reminds Travelers to Allow 72 Hours for ESTA. Why?
Should the .gitignore include an entry for .vscode when using Git and VSCode
Ignore Lightning Application with .forceignoreSalesforce CLI is not installed - it ain't soNo sfdx-project.json found in the root directory of your open project. Open a Salesforce DX project in VS CodeHow do I retrieve all the code from lightning?command 'sfdx.force.project.with.manifest.create' not foundCan I use git repo in old format and vscode in new source format?vscode/sfdx doesn't see my projectUnable to Retrieve Source from SandboxLightningComponentBundle “Not available for deploy for this API version” errorunable to create project in vscode
wadewegner has an example .gitignore file with the below content
.DS_Store
.sfdx
.project
.salesforce
.settings
node_modules
.idea
As part of his sfdx-simple app on GitHub.
Should this file include an entry for VSCode when using VSCode?
.vscode
salesforcedx git vs-code
asked 20 hours ago
RobsRobs
2,137533
add a comment |
wadewegner has an example .gitignore file with the below content
.DS_Store
.sfdx
.project
.salesforce
.settings
node_modules
.idea
As part of his sfdx-simple app on GitHub.
Should this file include an entry for VSCode when using VSCode?
.vscode
salesforcedx git vs-code
asked 20 hours ago
RobsRobs
2,137533
add a comment |
wadewegner has an example .gitignore file with the below content
.DS_Store
.sfdx
.project
.salesforce
.settings
node_modules
.idea
As part of his sfdx-simple app on GitHub.
Should this file include an entry for VSCode when using VSCode?
.vscode
salesforcedx git vs-code
asked 20 hours ago
RobsRobs
2,137533
wadewegner has an example .gitignore file with the below content
.DS_Store
.sfdx
.project
.salesforce
.settings
node_modules
.idea
As part of his sfdx-simple app on GitHub.
Should this file include an entry for VSCode when using VSCode?
.vscode
salesforcedx git vs-code
salesforcedx git vs-code
asked 20 hours ago
RobsRobs
2,137533
asked 20 hours ago
RobsRobs
2,137533
asked 20 hours ago
RobsRobs
2,137533
asked 20 hours ago
RobsRobs
2,137533
asked 20 hours ago
RobsRobs
2,137533
2,137533
add a comment |
add a comment |
3 Answers
3
active
oldest
votes
I typically do include .vscode in my .gitignore. That directory shouldn't be under version control.
You can also create a global .gitignore that applies across all projects, although that doesn't provide benefit for other users who clone your repo.
answered 19 hours ago
David ReedDavid Reed
36.3k72254
add a comment |
In general, you should not commit .sfdx or .vscode, as these files store configurations specific to the local computer's workspace. Committing these files may cause issues when migrating to a new computer or sharing between other developers. If you use another IDE, like Force.com IDE, also make sure you do not reference things like "Referenced Packages" or any other metadata cache directories.
answered 18 hours ago
sfdcfoxsfdcfox
257k12202445
add a comment |
It depends whether you want to share the settings inside the .vscode folder.
On our team, we don't put .vscode into the .gitignore file because we want to share our team's recommended settings, launch configurations, tasks and extensions between developers. If you have machine specific settings then that won't work so well.
If you only want to share some settings between developers then you can pick and choose which settings files to put into .gitignore. Recommended extensions are in .vscode/extensions.json, for example.
Whether you want to share these settings is somewhat dependent on what sort of repository it is. If it's an open source repository where everyone might want different configurations for their own workflows then maybe it's best not to check them into git. For teams where it's nice to have your configuration shared for a consistent workflow then it often works well to check them in.
answered 17 hours ago
olaneolane
885
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "459"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsalesforce.stackexchange.com%2fquestions%2f252391%2fshould-the-gitignore-include-an-entry-for-vscode-when-using-git-and-vscode%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
I typically do include .vscode in my .gitignore. That directory shouldn't be under version control.
You can also create a global .gitignore that applies across all projects, although that doesn't provide benefit for other users who clone your repo.
answered 19 hours ago
David ReedDavid Reed
36.3k72254
add a comment |
I typically do include .vscode in my .gitignore. That directory shouldn't be under version control.
You can also create a global .gitignore that applies across all projects, although that doesn't provide benefit for other users who clone your repo.
answered 19 hours ago
David ReedDavid Reed
36.3k72254
add a comment |
I typically do include .vscode in my .gitignore. That directory shouldn't be under version control.
You can also create a global .gitignore that applies across all projects, although that doesn't provide benefit for other users who clone your repo.
answered 19 hours ago
David ReedDavid Reed
36.3k72254
I typically do include .vscode in my .gitignore. That directory shouldn't be under version control.
You can also create a global .gitignore that applies across all projects, although that doesn't provide benefit for other users who clone your repo.
answered 19 hours ago
David ReedDavid Reed
36.3k72254
answered 19 hours ago
David ReedDavid Reed
36.3k72254
answered 19 hours ago
David ReedDavid Reed
36.3k72254
answered 19 hours ago
David ReedDavid Reed
36.3k72254
36.3k72254
add a comment |
add a comment |
In general, you should not commit .sfdx or .vscode, as these files store configurations specific to the local computer's workspace. Committing these files may cause issues when migrating to a new computer or sharing between other developers. If you use another IDE, like Force.com IDE, also make sure you do not reference things like "Referenced Packages" or any other metadata cache directories.
answered 18 hours ago
sfdcfoxsfdcfox
257k12202445
add a comment |
In general, you should not commit .sfdx or .vscode, as these files store configurations specific to the local computer's workspace. Committing these files may cause issues when migrating to a new computer or sharing between other developers. If you use another IDE, like Force.com IDE, also make sure you do not reference things like "Referenced Packages" or any other metadata cache directories.
answered 18 hours ago
sfdcfoxsfdcfox
257k12202445
add a comment |
In general, you should not commit .sfdx or .vscode, as these files store configurations specific to the local computer's workspace. Committing these files may cause issues when migrating to a new computer or sharing between other developers. If you use another IDE, like Force.com IDE, also make sure you do not reference things like "Referenced Packages" or any other metadata cache directories.
answered 18 hours ago
sfdcfoxsfdcfox
257k12202445
In general, you should not commit .sfdx or .vscode, as these files store configurations specific to the local computer's workspace. Committing these files may cause issues when migrating to a new computer or sharing between other developers. If you use another IDE, like Force.com IDE, also make sure you do not reference things like "Referenced Packages" or any other metadata cache directories.
answered 18 hours ago
sfdcfoxsfdcfox
257k12202445
answered 18 hours ago
sfdcfoxsfdcfox
257k12202445
answered 18 hours ago
sfdcfoxsfdcfox
257k12202445
answered 18 hours ago
sfdcfoxsfdcfox
257k12202445
257k12202445
add a comment |
add a comment |
It depends whether you want to share the settings inside the .vscode folder.
On our team, we don't put .vscode into the .gitignore file because we want to share our team's recommended settings, launch configurations, tasks and extensions between developers. If you have machine specific settings then that won't work so well.
If you only want to share some settings between developers then you can pick and choose which settings files to put into .gitignore. Recommended extensions are in .vscode/extensions.json, for example.
Whether you want to share these settings is somewhat dependent on what sort of repository it is. If it's an open source repository where everyone might want different configurations for their own workflows then maybe it's best not to check them into git. For teams where it's nice to have your configuration shared for a consistent workflow then it often works well to check them in.
answered 17 hours ago
olaneolane
885
add a comment |
It depends whether you want to share the settings inside the .vscode folder.
On our team, we don't put .vscode into the .gitignore file because we want to share our team's recommended settings, launch configurations, tasks and extensions between developers. If you have machine specific settings then that won't work so well.
If you only want to share some settings between developers then you can pick and choose which settings files to put into .gitignore. Recommended extensions are in .vscode/extensions.json, for example.
Whether you want to share these settings is somewhat dependent on what sort of repository it is. If it's an open source repository where everyone might want different configurations for their own workflows then maybe it's best not to check them into git. For teams where it's nice to have your configuration shared for a consistent workflow then it often works well to check them in.
answered 17 hours ago
olaneolane
885
add a comment |
It depends whether you want to share the settings inside the .vscode folder.
On our team, we don't put .vscode into the .gitignore file because we want to share our team's recommended settings, launch configurations, tasks and extensions between developers. If you have machine specific settings then that won't work so well.
If you only want to share some settings between developers then you can pick and choose which settings files to put into .gitignore. Recommended extensions are in .vscode/extensions.json, for example.
Whether you want to share these settings is somewhat dependent on what sort of repository it is. If it's an open source repository where everyone might want different configurations for their own workflows then maybe it's best not to check them into git. For teams where it's nice to have your configuration shared for a consistent workflow then it often works well to check them in.
answered 17 hours ago
olaneolane
885
It depends whether you want to share the settings inside the .vscode folder.
On our team, we don't put .vscode into the .gitignore file because we want to share our team's recommended settings, launch configurations, tasks and extensions between developers. If you have machine specific settings then that won't work so well.
If you only want to share some settings between developers then you can pick and choose which settings files to put into .gitignore. Recommended extensions are in .vscode/extensions.json, for example.
Whether you want to share these settings is somewhat dependent on what sort of repository it is. If it's an open source repository where everyone might want different configurations for their own workflows then maybe it's best not to check them into git. For teams where it's nice to have your configuration shared for a consistent workflow then it often works well to check them in.
answered 17 hours ago
olaneolane
885
answered 17 hours ago
olaneolane
885
answered 17 hours ago
olaneolane
885
answered 17 hours ago
olaneolane
885
885
add a comment |
add a comment |
Thanks for contributing an answer to Salesforce Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsalesforce.stackexchange.com%2fquestions%2f252391%2fshould-the-gitignore-include-an-entry-for-vscode-when-using-git-and-vscode%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
