Haskell stack and version control

I’m new to Haskell and Stack. When creating a new project using stack new which files should be checked in to git (or any other VCS)? The whole dir?

parsing git log output, preferably as xml

Git produces “BUG: There are unmerged index entries”

How to display metainformation about single commit in git

How to apply a very old patch in Git?

git recover single file that was deleted during a merge

Why GitHub suggest “prefix your version names with the letter v?”

How do i make a non-bare git repository into a bare one?

How can I make it so git rejects pushing code that won't compile?

Take only part of a git commit, push to github

git checkout -f master VS git reset

Git: new branch not getting pushed

what are possible ways of referring to a git stash?

One Solution collect form web for “Haskell stack and version control”

You should check in stack.yaml, your-project-name.cabal and Setup.hs, as they are necessary for building your project in a reproducible way. The src, app and test directories should also be committed, as they in principle are where your source code will live (you can of course rearrange the structure of the default project if you wish to do so). On the other hand, you should ignore the .stack-work directory, as it contains the build output and other volatile pieces of data.

Haskell stack and version control

One Solution collect form web for “Haskell stack and version control”

Jenkins PHP Job Failing

What happens to source and destination branches after git merge?

Git commit message

Use git command to get the hash of the commit that changed a file

How to access the remote parent branch of my local branch with GitPython or similar library?

Git ignore unignore not working?

Structuring Go subpackages for teams

What is the difference in command line argument syntax between bat and sh?

Distributed version control for HUGE projects – is it feasible?

Using TortoiseHg to push to an authenticated git repository