Skip to content

Ignore the .cache folder for LabVIEW projects#2694

Merged
shiftkey merged 1 commit intogithub:masterfrom
shastriUF:patch-1
Jun 17, 2018
Merged

Ignore the .cache folder for LabVIEW projects#2694
shiftkey merged 1 commit intogithub:masterfrom
shastriUF:patch-1

Conversation

@shastriUF
Copy link
Copy Markdown
Contributor

Ignore the .cache folder for LabVIEW projects.

Reasons for making this change:

.cache/ is a local folder with metadata used by LabVIEW NXG.

Ignore the .cache folder for LabVIEW projects. This is a local folder with metadata used by LabVIEW NXG.
@shiftkey
Copy link
Copy Markdown
Member

shiftkey commented May 9, 2018

@shastriUF any links to StackOverflow discussions or other documentation about this change?

@shastriUF
Copy link
Copy Markdown
Contributor Author

shastriUF commented May 10, 2018

@shiftkey I couldn't find any public discussions. One example I found was in the repo of LabVIEW NXG examples that NI maintains. This repo ignores the .cache folder in this commit.

Note that they change the .gitignore later so that they can commit .projectcache files in the .cache folder. However, these cache files are binary files, so we wouldn't want to recommend committing them by default.

I don't think I can find any other public documentation. Is there a way to say "I work for the team/company that builds this language" as a means of authenticating these changes? :)

@shiftkey
Copy link
Copy Markdown
Member

Is there a way to say "I work for the team/company that builds this language" as a means of authenticating these changes? :)

@shastriUF having this context up front definitely helps, but being able to point people to resources about this rule and why it's needed it preferred.

@shiftkey shiftkey merged commit 42223b3 into github:master Jun 17, 2018
@shastriUF shastriUF deleted the patch-1 branch June 17, 2018 18:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants