deploying to is called 'heroku', although this isn't heroku-specific # We'll create a commit on ...
files from subdirectories and only kept the top-level .gitignore file.
We had some ZIP files in our Code-Repo, which I started tracking with
Check: ~/.gitignore; The .gitignore within the directory itself and any parent directories (not just the repository root); ~/.config/git/ignore ...
When creating a model, and making the controller and migration for it
Issues are a great way to keep track of tasks, enhancements, and bugs
gitattributes is not designed for this purpose. It can support only path. it couldn't support size, mime types, scripts, etc. This is a question for "git-lfs ...
Created a repository on GitHub, or have an existing repository owned by someone
What makes this issue even weirder is that it is not completely reproducible.
The first response might be to simply use Git-LFS (Git Large File