在GIT中处理Rails db / schema.rb文件的正确方法是什么？

是的， schema.rb 是一个生成的文件，但它只是在您的文本编辑器生成 pancakes.rb 模型文件或未编辑脚手架文件。

是的，您可以重建<$ c $通过构建一个新的数据库，然后运行所有的迁移，创建一个名为schema.rb 的文件。但是，您应该立即清理旧的迁移，以避免在每次 rake db：migrate >时检查数百个迁移文件，以便重建并运行所有迁移在高度活跃的项目中往往不是一种选择。

Should we include schema.rb while commiting to GIT? or should we ignore it? what is the right approach?

Well the standard schema.rb file for Rails 2 has this at the end of the comment block at the top of the file:

The Rails 3 schema.rb that I have kicking around says the same thing. I think the comment says it all.

Update in response to comments: Yes, mistakes can be made and you can get conflicting changes and bugs mangling your schema.rb but that's why you want it under revision control, revision control allows you to keep track of everything and backup when needed. There is only one thing in your entire source tree that specifies your database schema and that is schema.rb. Your database schema absolutely is a critical artifact and anything that important needs to be tracked in revision control.

Any update/merge problems with schema.rb should be sorted out just by sorting out your conflicting migrations so schema.rb will get fixed as a side effect of fixing the real problem.

Yes, schema.rb is a generated file but it is only generated in the sense that your text editor generates your pancakes.rb model file or an unedited scaffold file is generated.

Yes, you could rebuild your schema.rb file by building a new database and then running all of your migrations. But, you should clear out your old migrations now and then to avoid having to check hundreds of migration files every time you rake db:migrate so "rebuild and run all the migrations" often isn't an option in a highly active project.