vscode-docs/.gitattributes

* text=auto eol=lf
*.gif filter=lfs diff=lfs merge=lfs -text
*.mp4 filter=lfs diff=lfs merge=lfs -text
*.jpg filter=lfs diff=lfs merge=lfs -text
*.png filter=lfs diff=lfs merge=lfs -text
*.md diff=markdown

# Fine-tune GitHub's language detection
docs/** -linguist-documentation
*.md linguist-detectable
Add section on using env vars to mount your home folder Per discussion in https://github.com/microsoft/vscode-remote-release/issues/306#issuecomment-492237498 2019-05-14 17:40:21 +03:00			`* text=auto eol=lf`
Track gif, mp4, png and jpg files in lfs 2019-03-11 23:56:41 +03:00			`*.gif filter=lfs diff=lfs merge=lfs -text`
			`*.mp4 filter=lfs diff=lfs merge=lfs -text`
			`*.jpg filter=lfs diff=lfs merge=lfs -text`
			`*.png filter=lfs diff=lfs merge=lfs -text`
.gitattributes: mark '*.md' as Markdown files Denote Markdown files as such with the 'diff' Git attribute [1]. This allows various Git commands (diff [2, 3], grep [4, 5], log [6], blame [7]) to show in which part of the "code" the changes are located in the hunk header, i.e. the previous commit would be shown as diff --git a/docs/remote/troubleshooting.md b/docs/remote/troubleshooting.md index bfcf303b7..5ab4f6e60 100644 --- a/docs/remote/troubleshooting.md +++ b/docs/remote/troubleshooting.md @@ -516,8 +516,9 @@ ### Cleaning up the VS Code Server on the remote If you want to run these steps manually, or if the command isn't working for you, you can run a script like this: ```bash -kill -9 `ps ax \| grep "remoteExtensionHostAgent.js" \| grep -v grep \| awk '{print $1}'` -kill -9 `ps ax \| grep "watcherService" \| grep -v grep \| awk '{print $1}'` +# Kill server processes +kill -9 `ps aux \| \grep vscode-server \| \grep USER \| \grep -v grep \| awk '{print $2}'` +# Delete related files and folder rm -rf ~/.vscode-server # Or ~/.vscode-server-insiders ``` Notice how the hunk header indicates the changes are in the "Cleaning up the VS Code Server on the remote" section. The history of that specific entry can now be interrogated using git log -L:"Cleaning up":docs/remote/troubleshooting.md [1] https://git-scm.com/docs/gitattributes#_defining_a_custom_hunk_header [2] https://git-scm.com/docs/git-diff#_generating_patch_text_with_p [3] https://git-scm.com/docs/git-diff#Documentation/git-diff.txt--W [4] https://git-scm.com/docs/git-grep#Documentation/git-grep.txt--p [5] https://git-scm.com/docs/git-grep#Documentation/git-grep.txt--W [6] https://git-scm.com/docs/git-log#Documentation/git-log.txt--Lltfuncnamegtltfilegt [7] https://git-scm.com/docs/git-blame#Documentation/git-blame.txt--Lltfuncnamegt 2022-03-25 19:49:09 +03:00			`*.md diff=markdown`
Fine-tune GitHub's language detection for the repo Since the whole repo is dedicated to documentation, documentation is the "source code" of this repo. In order to capture this in language stats (and potentially attract more contributors): 1. Consider `docs/` folder "source", not documentation. 2. Count all Markdown files as "source". 2024-03-19 13:35:00 +03:00
			`# Fine-tune GitHub's language detection`
			`docs/** -linguist-documentation`
			`*.md linguist-detectable`