kandi X-RAY | gitignore.io Summary
kandi X-RAY | gitignore.io Summary
.gitignore.io is a web service designed to help you create .gitignore files for your Git repositories. The site has a graphical and command line method of creating a .gitignore for your operating system, programming language, or IDE. Source templates for gitignore.io:
Top functions reviewed by kandi - BETA
gitignore.io Key Features
gitignore.io Examples and Code Snippets
Trending Discussions on gitignore.io
I have a following case:
I made a
.idea folder and
project_name.iml were not in the ignore list and were pushed into the repo. I added them into the
.gitignore, but they remain in the repo. If I make any changes to them, they appear in the list of changed files to commit.
There is a way to get rid of them through the terminal
ANSWERAnswered 2022-Apr-04 at 09:59
- Remove the file/folder in Project tool window via the "del" key:
- Invoke "Undo" action to get them back. You will be asked if you want to add the files to git.
- Click "NO"
- Commit changes. The removed/re-added folder will be removed from git in the scope of this commit.
I'm creating an Ionic project using Capacitor (formerly Cordova) and added Android as a target.
I've been able to build the app and add the Android target, which creates a bucketload of files under
ANSWERAnswered 2020-Aug-16 at 17:11
Is there anything that needs to be saved to the repo in the ionic android directory?
I would suggest that you include your native folders in your repo as well.
Based on my experience with capacitor over the past year while developing two applications, consider these things.
- Most of the times you will be using at least a few cordova plugins, since capacitor still doesn't have a viable plugin for certain features.
- These plugins, will require you to manually add some variables ( like sdk keys ) or initialization function on the native side of the codes.
- In fact, even for capacitor community plugins ( which are plugins created by other samaritans ), you will have to add some minimum lines of code to the native side. Consider this plugin for facebook sign in. Just go through the installation steps, you will see a long list of configurations on both ios and android sides.
- Capacitor is not formerly Cordova. Both of these are different frameworks. Capacitor completely depends on native ide's for compilation, whereas cordova cli could build the native codes for you (ios, mac required).
but if someone clones the repo, they can rebuild the entire Android directory from scratch, right?
When your application grows, depending on its intended functionality, this would not be an easy task. They will have to go through all these minor tweaks to get it working.
All in all, put your native code in the repo as well. For me, the repository size with the native codes is not terribly huge.
I was wondering which files of a project should committed to a repository. For example, i've created the gitignore file for a project of mine, a java web app created with NetBeans. On gitignore.io i put the netbeans tag but i noticed that there's some files likes .properties or build.xml still not ignored. Should i ignore those ones too or not? And the META-INF and WEB-INF should be ignored too?
Thanks in advance...
ANSWERAnswered 2020-Aug-04 at 19:53
you can put this to your .gitignore:
I can not prove to the management the futility and even harm of saving IDE specific files and folders in GitHub
There is even a problem in the deliberate mixing of two different issues:
- I want to use Eclipse;
- If we use Eclipse, then its files should be stored in the repository;
I tried everything:
- from "files not related to the project should not be there"
- to "every developer knows how to configure their IDE for the project based on the pom.xml"
- and "if two programmers use two different IDEs, should their files also be saved?"
- and so on... like "specially designed gitignore.io provides recommended gitignore based on what you are using."
What arguments can be given besides “no one does that for a long time because it's obvious”.
PS. I am not going to start another holy war, I need arguments that are clear to the management....
ANSWERAnswered 2020-Jun-25 at 16:53
The rule is not do not share IDE-specific files, but as long as tool-specific files are maintained, they should be shared, even if they are not used by everyone.
This applies to specific files of GitHub, Jenkins, FindBugs/SpotBugs, Eclipse and other tools. The presence of these files does not harm (files and folders starting with a dot meant to be hidden). This is well documented (e.g. here for Eclipse) and after all, the tools do not place these files in the project directory for no reason, although it would be possible otherwise, but because they are meant to be shared.
However, there are still people who believe that there should be one Maven-specific
pom.xml file only, which is focused on building only. But since none of them is a tool developer and none of them has never convinced the tool developers, it is very unlikely that you will convince your management.
Also be aware that Eclipse-specific files are not specific to the Eclipse IDE, as they are also used by e.g. VS Code. Eclipse-specific are not even IDE-specific, since, for example, the Eclipse compiler for Java (ecj) can be used as a linter inside a build to run on a server.
I am working on a Powershell script that does the following:
- Pulls down git ignore patterns from https://gitignore.io
- Reads custom git ignore patterns from a text file on the filesystem
- Appends both to a
.gitignorefile on disk, overwriting previous contents.
The end result should be a file with gitignore.io patterns PLUS any custom defined patterns from another file.
Here is what I've come up with so far:...
ANSWERAnswered 2020-Jan-31 at 15:45
Wrap both statements in an array subexpression
@(), and pipe to
No vulnerabilities reported
Reuse Trending Solutions
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page