What sort of file should not be put into a source code repository?

Hand written text files should be kept in the repository. Generated files are not good idea to put them in repository as they mess up your history.

What types of files should and should not be committed to source control?

The list includes things like:

• source files.
• make, project, and solution files.
• other build tool configuration files (not user related)
• 3rd party libraries.
• pre-built files that go on the media like PDFs & documents.
• documentation.
• images, videos, sounds.
• description files like WSDL, XSL.

Should you commit IDE files?

I know this is an unpopular advice but: commit the IDE project files in the repository. Once a member has a successful local setup, the files should be committed so that everyone else can just checkout/update, and get the project running.

Which types of files are not suitable for being version controlled?

Version control is intended for files that people edit. Generated files should not be committed to version control. For example, do not commit binary files that result from compilation, such as .o files or . class files.

What files should you keep under source control?

5 file categories you should store

• source code files such as .
• build tool configuration files such as mvn.
• DevOps tools configuration such as Dockerfile, Jenkinsfile, Vagrantfile,
• infrastructure code required to install and run your software such as: Bash, Ansible, Terraform scripts.

What files should not be stored in git?

Files that don’t belong to the project. Files like .

Files that are automatically generated. This includes files from preprocessors (like Sass to CSS).

Libraries. If you don’t use a package manager, you should check in your libraries.

Credentials.

Should IML files be committed?

So now in 2016 the the answer would be “No, its not mandatory to save . iml files in Version Control System.” Personally, I’ve found that Android Studio is constantly making minor rearrangements and alterations to the . iml files, so maintaining them in version control is a hassle.

Should .settings be checked in?

The . settings folder is for settings that apply to the project. You should keep it under your source control system if you want every user who checks out the project in another workspace to have the same project settings.

How do you handle source control?

Source code management best practices

1. Commit often. Commits are cheap and easy to make.
2. Ensure you’re working from latest version. SCM enables rapid updates from multiple developers.
3. Make detailed notes. Each commit has a corresponding log entry.
4. Review changes before committing.
5. Use Branches.
6. Agree on a Workflow.

Should images be in source control?

Images and visual assets do not have a “source,” so they should be tracked in version control.

Should IML files be in version control?

Should I add IML file to Git?

*. iml files are not really needed and can be gitignore’d. iml files are created by IntelliJ IDEA based on the pom. xml file read by Maven to resolve dependencies of the project.

How do I ignore a specific file in an IDE?

As @Michael says, you can generate a set of files to ignore in base of IDE that you are using, take a look at this link, for example for eclipse (click here to generate) copy and paste the configuration within your .gitignore file.

What file types are used by the Eclipse IDE?

The .classpath file, .project file, and .settings/ directory are used by the Eclipse IDE. There are differing opinions about putting IDE-specific project files under source control.

How do I ignore all ideas in a project?

You can simply ignore all of them by adding .idea/* to the .gitignore file. While maintaining the proper .gitignore file is helpful, I found this alternate approach is way cleaner and easier to use. Create dummy folder my_project and inside that git clone my_real_project the actual project repo.

Does my_project/idea pollute my Git repo?

You can see my_project/.idea wouldn’t pollute your git repo because it happily lives outside the git repo which is what you want. This way your .gitignore files stays clean as well. This approach works better due to the below reasons.