"Checked in but not viewable" is called a private repo.
If it's a public repo, don't check it in. I don't think Github should try to create a manifest of all "dangerous" files.
Really, best practice is to not check in sensitive values to your repository, ever, and instead use environment variables or symlinks to shared files via Capistrano to set these values in your application.
Comments
`rails new foo` generates a `.gitignore` file. That's where this belongs.
Not entirely, because you do need the file to startup your application. Which makes it a concern that should be checked in imo.
Just not publicly viewable
"Checked in but not viewable" is called a private repo.
If it's a public repo, don't check it in. I don't think Github should try to create a manifest of all "dangerous" files.
Really, best practice is to not check in sensitive values to your repository, ever, and instead use environment variables or symlinks to shared files via Capistrano to set these values in your application.