-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support p4ignore #53
Comments
@unional I wasn't sure how to contact you. But I've made you a collaborator on this project, in case you want to push directly to the repo. side note: I am not using Atom right now (and I'm primarily using git -- though still inside perforce), so my activity on this project may be a bit slow. |
sorry just now thought about the actual topic. why don't you want to check in your .p4ignore file? |
:) Sorry I didn't make it clear in my original message. What I meant is changing the files specified in e.g., I want to ignore |
OK, that makes sense. |
A good support of .p4ignore should also comply to the Exclude VCS Ignored Paths setting, ie. if checked, they should disappear from the tree-view and from the searches. Currently, I use the atom-tree-ignore package for that, duplicating part of the .p4ignore content, and it doesn't support hiding from searches. The above package uses the ignore NPM library to support .gitignore-like rules. Not sure exactly how .p4ignore rules differ from these, for practical purposes (ie. if they are a subset of the former, that's OK to use). |
https://www.perforce.com/blog/120214/new-20121-p4ignore
Currently
atom-perforce
will try to add the file every time I save the file.The text was updated successfully, but these errors were encountered: