Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add more haskell build artifacts to .gitignore #46

Closed
wants to merge 2 commits into from

Conversation

chessai
Copy link
Member

@chessai chessai commented Jun 24, 2019

I was surprised to see the .gitignore so bare. I guess most contributors just have these in their global .gitignores? I think having these would be beneficial, and make it easier to stop build artifacts from muddying the tree.

Copy link
Member

@RyanGlScott RyanGlScott left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@hvr is pickier about .gitignore files than I am, so I'll let him make the final call here. Otherwise, LGTM.

.gitignore Outdated Show resolved Hide resolved
ghc.mk
*.hi
*.o
.ghc.environment*
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fwiw, if we're adding more stuff, I'm also missing /cabal.project.local and possibly /cabal.project.freeze

@hvr
Copy link
Member

hvr commented Jun 26, 2019

In general, I tend to add .gitignores as I notice them (and I tend to be rather minimal about them); and yes, there is also the convention to add certain ubiqutous patterns to your $HOME/.config/git/ignore... :-)

@chessai
Copy link
Member Author

chessai commented Jun 20, 2020

I think in practise this doesn't cause any issues. I use a global .gitignore now. Anyone feel free to re-open if they think this is a good addition

@chessai chessai closed this Jun 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants