reference.php revisited #64579
|
I know reference.php has already been discussed, but it's been a while now since it was introduced, so we've had time to get used to it, but I still have questions, so I figured I'd bring the topic back up again. My basic question is this: Given that reference.php is autogenerated by doing pretty much anything, including composer install / update, why do we need to commit it? It's always going to be there anyway, so why keep it in git? More importantly, the existence of reference.php and the fact that it constantly gets regenerated is causing us real problems day-to-day. eg When switching branches, people often forget to (or don't bother to) do a composer update. This has resulted in several bad commits with reference.php getting regenerated and committed inadvertently, also leading to merge conflicts. It's all resolvable of course, but it's causing us friction in our dev process and it feels unnecessary. The obvious solution is simply to gitignore the file. It gets re-generated anyway, so I don't see the problem. But it begs the question why the recommendation to add it to git in the first place? Is there something I'm missing that makes my gitignore plan a bad idea? |
Replies: 2 comments
|
IIRC the only advantage I’ve seen mentioned about committing this file is being able to keep track of configuration updates (especially now that its generation stabilized). If that doesn’t outweigh the cons (which I guess is the case!) there is no issue in ignoring it: #62658 (comment) |
|
For the record, we decided to not commit it and life is so much easier... |
IIRC the only advantage I’ve seen mentioned about committing this file is being able to keep track of configuration updates (especially now that its generation stabilized).
If that doesn’t outweigh the cons (which I guess is the case!) there is no issue in ignoring it: #62658 (comment)