Skip to content

Instantly share code, notes, and snippets.

@octocat
Created February 27, 2014 19:38
Star You must be signed in to star a gist
Save octocat/9257657 to your computer and use it in GitHub Desktop.
Some common .gitignore configurations
# Compiled source #
###################
*.com
*.class
*.dll
*.exe
*.o
*.so
# Packages #
############
# it's better to unpack these files and commit the raw source
# git has its own built in compression methods
*.7z
*.dmg
*.gz
*.iso
*.jar
*.rar
*.tar
*.zip
# Logs and databases #
######################
*.log
*.sql
*.sqlite
# OS generated files #
######################
.DS_Store
.DS_Store?
._*
.Spotlight-V100
.Trashes
ehthumbs.db
Thumbs.db
@iollmann
Copy link

iollmann commented Jan 19, 2023

It is often useful to add xcuserdata to avoid having one user's machine randomly perturb Xcode debugging switches every time there is a git pull, or to be alerted that changing that stuff will necessitate a push. We also don't really need to see our collaborators xcuserdata.

@Artem9444
Copy link

gitignore

@vinyll
Copy link

vinyll commented Jan 24, 2023

Anything that is specific to you OS, you editor or your workspace should be in your system’s home gitignore, not the project’s .gitignore.

The project´s .gitignore should remain clean with only file and path that are specific to the project itself, not your development environment.

Copy link

ghost commented Mar 5, 2023

I have created a fork to ignore these extra files:
*.pyo, *.pyc, *~, *.bak, and *.swp, here.

@renalupo
Copy link

renalupo commented Mar 6, 2023

ciao

@renalupo
Copy link

renalupo commented Mar 6, 2023

assort

@renalupo
Copy link

renalupo commented Mar 6, 2023

ciao

@renalupo
Copy link

renalupo commented Mar 6, 2023

ahooo

@67788804
Copy link

Hello

@rajdip20
Copy link

Thanks for the information.

@AddonGrp
Copy link

Thank´s

@SergeNoah000
Copy link

et si c'est pour un dossier ou un sous-dossier ?

@Klkl121aaaa
Copy link

It is often useful to add xcuserdata to avoid having one user's machine randomly perturb Xcode debugging switches every time there is a git pull, or to be alerted that changing that stuff will necessitate a push. We also don't really need to see our collaborators xcuserdata.

Klkl121aaaa

@Klkl121aaaa
Copy link

Qwqw12121a

@Klkl121aaaa
Copy link

@mohammad-oghli
Copy link

Nicely done!

@67788804
Copy link

c'est Bon vraiment.merci beaucoup

OK 👍👍👍 super

@Aleksanrd140792
Copy link

👍🏻👍🏻👍🏻👍🏻👍🏻

@Aleksanrd140792
Copy link

Ďakujem

@iollmann
Copy link

Anything that is specific to you OS, you editor or your workspace should be in your system’s home gitignore, not the project’s .gitignore.

The project´s .gitignore should remain clean with only file and path that are specific to the project itself, not your development environment.

On this we disagree. If I own the project and don't want to see users' xcconfig files or let them change mine, then that .gitignore should contain xcuserdata. I can't rely on them to set that in their own system consistently.

@Regis8689
Copy link

.gitignore

@srabon664
Copy link

Ok

@qwerty13
Copy link

For Excluding Temp and Output Directories, We Can use This:

# Build results #
###################
[Oo]utput/
[Tt]emp/

@Rafka931
Copy link

Rafka931 commented Dec 9, 2023

I have created a fork to ignore these extra files:
*.pyo, *.pyc, *~, *.bak, and *.swp, here.

@diegillos
Copy link

Live

@chrismcintosh78
Copy link

what about folders we want to ignore?

@1C0D
Copy link

1C0D commented Jan 2, 2024

and a folder?

@1C0D
Copy link

1C0D commented Jan 2, 2024

@chrishmorris folderName/ but if it was already in the repo must be detached of git at first $ git rm -r folderName/

@syawal400
Copy link

Kuakuakaukauakua

@Andrew237wilson
Copy link

<!DOCTYPE html>
<html>
<head>
    <title>23 Seven Recovery</title>
    <!-- CSS stylesheets and other dependencies -->
    <link rel="stylesheet" type="text/css" href="styles.css">
    <script src="main.js"></script>
</head>
<body>
    <!-- Header section -->
    <header>
        <nav>
            <!-- Logo and navigation menu -->
        </nav>
    </header>

    <!-- Hero section -->
    <section id="hero">
        <!-- Hero content and call to action buttons -->
    </section>

    <!-- Success Stories section -->
    <section id="success-stories">
        <!-- Display success stories with pictures and stories -->
        <!-- Include a form for users to submit their own success stories -->
    </section>

    <!-- Helpful Information section -->
    <section id="helpful-information">
        <!-- Display helpful information related to recovery and life-changing -->
        <!-- Include a form for users to submit helpful information -->
    </section>

    <!-- Video Chat section -->
    <section id="video-chat">
        <!-- Integrate a video chat platform for users to connect with each other -->
        <!-- Provide options for users to request video chats in times of need -->
    </section>

    <!-- Payment section -->
    <section id="payment">
        <!-- Include payment options such as credit cards, Cash App, PayPal, Apple Pay, Google Pay -->
        <!-- Provide a form for users to complete payments -->
    </section>

    <!-- Personal Account section -->
    <section id="personal-account">
        <!-- Include a link to your personal account where you can manage finances -->
        <!-- Provide options for users to send, receive, and obtain money -->
        <!-- Include a form to link personal accounts -->
    </section>

    <!-- Footer section -->
    <footer>
        <!-- Footer content and links -->
    </footer>
</body>
</html>

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment