Add a bunch of ignore patterns for vim #567
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
From https://github.com/github/gitignore/blob/master/Global/Vim.gitignore Motivated by the fact that a .swp file appeared in a PR. We probably don't need all of these, but it looks like they should be safe to include (i.e., I can't imagine a real file having a name like one of these patterns, given that most of them begin with '.' or '_').
ekluzek
approved these changes
Dec 10, 2018
|
Like other's I might put this on the release branch first. |
ekluzek
added
the
PR status: ready
ekluzek
added a commit
to ekluzek/CTSM
that referenced
this pull request
Jan 15, 2019
|
I've put this on the release branch. |
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.
From
https://github.com/github/gitignore/blob/master/Global/Vim.gitignore
Motivated by the fact that a .swp file appeared in a PR. We probably
don't need all of these, but it looks like they should be safe to
include (i.e., I can't imagine a real file having a name like one of
these patterns, given that most of them begin with '.' or '_').
Specific notes
Contributors other than yourself, if any: none
CTSM Issues Fixed (include github issue #): none
Are answers expected to change (and if so in what way)? no
Any User Interface Changes (namelist or namelist defaults changes)? no
Testing performed, if any: none