GitIgnore File for archive

# Created by https://Shodkk.com/create-gitignore (Shantanu Bombatkar) SirDeploy Package # It helps deploy fakeserver ReactApp on Heroku and Github Pages # Hope it helps || Thanks for Using SirDeploy Package ### Archive ### ### Mostly from https://en.wikipedia.org/wiki/List_of_archive_formats ## Archiving only # The traditional archive format on Unix-like systems, now used mainly for the creation of static libraries. *.a *.ar # RPM files consist of metadata concatenated with (usually) a cpio archive. Newer RPM systems also support other archives, as cpio is becoming obsolete. cpio is also used with initramfs. *.cpio # A self-extracting archive that uses the Bourne shell (sh). *.shar # A system for storing multiple files. LBR archives typically contained files processed by SQ, or the archive itself was compressed with SQ. LBR archives that were compressed with SQ ended with the extension .LQR *.LBR # An archive format originally used mainly for archiving and distribution of the exact, nearly-exact, or custom-modified contents of an optical storage medium such as a CD-ROM or DVD-ROM. However, it can be used to archive the contents of other storage media, selected partitions, folders, and/or files. The resulting archive is typically optimized for convenient rendering to (re-)writable CD or DVD media. *.iso # A library format used primarily on the Commodore 64 and 128 lines of computers. This bears no resemblance to the DOS LBR format. While library files were quick to implement (a number of programs exist to work with them) they are crippled in that they cannot grow with use: once a file has been created it cannot be amended (files added, changed or deleted) without recreating the entire file. *.lbr # An archive format used by Mozilla for storing binary diffs. Used in conjunction with bzip2. *.mar # A common archive format used on Unix-like systems. Generally used in conjunction with compressors such as gzip, bzip2, compress or xz to create .tar.gz, .tar.bz2, .tar.Z or tar.xz files. *.tar # Package managers # Red Hat Package Manager *.rpm # Debian package *.deb # MicroSoft Installer *.msi *.msm *.msp # Mozilla package installer *.xpi # Ruby Package *.gem # Star the Repo https://github.com/shaantanu9/SirDeploy # https://www.linkedin.com/in/shantanu-bombatkar/ # End of File

List Of Files and Folders That Get Ignored using this Gitignore code

Above Code Helps ignore following files from archive Project

The traditional archive format on Unix-like systems, now used mainly for the creation of static libraries.

RPM files consist of metadata concatenated with (usually) a cpio archive. Newer RPM systems also support other archives, as cpio is becoming obsolete. cpio is also used with initramfs.

A self-extracting archive that uses the Bourne shell (sh).

A system for storing multiple files. LBR archives typically contained files processed by SQ, or the archive itself was compressed with SQ. LBR archives that were compressed with SQ ended with the extension .LQR

An archive format originally used mainly for archiving and distribution of the exact, nearly-exact, or custom-modified contents of an optical storage medium such as a CD-ROM or DVD-ROM. However, it can be used to archive the contents of other storage media, selected partitions, folders, and/or files. The resulting archive is typically optimized for convenient rendering to (re-)writable CD or DVD media.

A library format used primarily on the Commodore 64 and 128 lines of computers. This bears no resemblance to the DOS LBR format. While library files were quick to implement (a number of programs exist to work with them) they are crippled in that they cannot grow with use: once a file has been created it cannot be amended (files added, changed or deleted) without recreating the entire file.

An archive format used by Mozilla for storing binary diffs. Used in conjunction with bzip2.

A common archive format used on Unix-like systems. Generally used in conjunction with compressors such as gzip, bzip2, compress or xz to create .tar.gz, .tar.bz2, .tar.Z or tar.xz files.

Package managers

Red Hat Package Manager

Debian package

MicroSoft Installer

Mozilla package installer

Ruby Package

What is GitIgnore File?

GitIgnore is a file that tells Git which files or folders to ignore in a project. It is used to avoid committing unwanted files to a Git repository such as temporary files created by the editor vi or temporary build files. It is also used to avoid committing sensitive information such as passwords or API keys to a public repository.

How to Create GitIgnore File?

Creating getting a file is quite simple you just need to create a normal file you can use touch dot Gitignore or you can create it from VS code or any editor you are using or you can directly create from your explorer. Just create a file where you don't need to give the name to the file just use dot get ignore

How to Create GitIgnore File?

How to use GitIgnore File to Ignore Files?

To Use Gitignore File just paste the file downloaded file to the root of the github repo, no need to configure anything. Just paste the file and you are good to go. If the code is push first you can clear the cache of the git by using git rm -r --cached . and then push the code again.

How to use GitIgnore File to Ignore Folders?

There is simple rules to ignoring folders in Gitignore file. Just add the folder name in the gitignore file and you are good to go. If you want to ignore the folder and all the subfolders then you can use /foldername/ and if you want to ignore the folder and all the subfolders and files then you can use /foldername/*. for example if you want to ignore the node_modules folder and all the subfolders and files then you can use /node_modules/* and if you want to ignore the node_modules folder and all the subfolders then you can use /node_modules/

How to use GitIgnore File to Ignore Files and Folders?

To ignore files and folders in Gitignore file you can use the same rules as we have used to ignore the folders. Just add the file name or folder name in the gitignore file and you are good to go. If you want to ignore the folder and all the subfolders then you can use /foldername/ and if you want to ignore the folder and all the subfolders and files then you can use /foldername/*. for example if you want to ignore the node_modules folder and all the subfolders and files then you can use /node_modules/* and if you want to ignore the node_modules folder and all the subfolders then you can use /node_modules/

Why GitIgnore File not Working?

There are many reasons why Gitignore file is not working. The most common reason is that you have not added the file to the root of the github repo. If you have added the file to the root of the github repo then you can clear the cache of the git by using git rm -r --cached . and then push the code again. Or there are some rules for gitignore file to work properly. You can check the rules here.

Rules for GitIgnore File

There are some rules for gitignore file to work properly. You can check the rules here. To Avoid the Gitignore file not working you can follow the rules. Rule 1 The File that you already pushed on github you can't ignore it. Rule 2 Folder name should be in the gitignore file. Rule 3 If you want to ignore the folder and all the subfolders then you can use /foldername/ and if you want to ignore the folder and all the subfolders and files then you can use /foldername/*. for example if you want to ignore the node_modules folder and all the subfolders and files then you can use /node_modules/* and if you want to ignore the node_modules folder and all the subfolders then you can use /node_modules/ Rule 4 If you want to ignore the file then you can use the file name in the gitignore file. Rule 5 If you want to ignore the file and all the subfolders then you can use /filename/ and if you want to ignore the file and all the subfolders and files then you can use /filename/*. for example if you want to ignore the package-lock.json file and all the subfolders and files then you can use /package-lock.json/* and if you want to ignore the package-lock.json file and all the subfolders then you can use /package-lock.json/

GitIgnore File for archive

Create a .gitignore file to tell git which files or folders to ignore in your archive project.

List Of Files and Folders That Get Ignored using this Gitignore code

Create GitIgnore File

What is GitIgnore File?