It's your (collectively - 5 of you) module, presumably you've discussed this amongst the maintainers and decided this is the best approach, so it's up to you. gitignore file and also added to the svn:ignore properties for VCS.
I see no real problems in keeping this, though it should be moved toward the bottom of the. This change actually snuck in under the radar via r35242. gitignore is helpful for people using the PhpStorm IDE. gitignore settings so that everyone else inherits them is, I would have thought, not best-practice in a public repo.Īnyway, just my 2p. idea folder in the root folder to store project configuration etc. However, with the greatest of respect (because I'm every grateful for this module), surely a maintainer's task is to run a public contributed module in whatever way is best for all users of the module, as constrained by its intended use-case. > When you are maintainer - adding gitignore saves a lot of time.
gitignore file, also find it causes problems to have a project that uses its own one. I'm sure other people, who have their own development environments and wish to use their own. Too many of those, there's then a danger that I start ignoring red flags that are genuine issues, because I've got too used to seeing the false alerts. Only it shouldn't actually be present, so I'm getting a red flag in Hacked when actually nothing's amiss. If I then use Hacked to check to ensure that I'm using correct versions of all files, it always flags up the Date module as not having the file ".gitignore" that should be present. When I create a development copy of a site to work on it, I use drush rsync, which does not copy across. I use quite a lot of contrib modules and themes, and Date is the only one that has a. Start command palette (with Ctrl+Shift+P or F1) and start typing Add gitignore. gitignore by pulling file from the the github/gitignore repository.
Phpstorm gitignore code#
A extension for Visual Studio Code that assists you in working with. > I suppose your gitignore file was causing problems for people using your module. gitignore extension for Visual Studio Code. gitignore file ever to be committed to the master repository. Those needs will be different for each developer who works on their own fork, so I'd presume it's bad practice for a. gitignore file to determine what files within that working directory will be ignored by local git commands. It seems to me that, when you clone a repository to work on it, you create your own. phpstorm+all,phpstorm+iml,pimcore,pinegrow,platformio. I know this is marked as "won't fix", but I'll still add a comment here to say "+1" After the function is created, the gi command will give you command line access to the gitignore.io API.