Since Hexo will never read _multiconfig.yml directly (It will be overriden every time hexo g is executed), there should be no conflict.

@SukkaW Thanks for your comment.

Yes, there will be not problem to serve or build, but it will confuse users when there's an untracked file which is not added by themself.

If this file is added to the source code with git add, others or the server will still generate this file. Although the content will be the same, if the operation systems or file systems are not all identical (ie: windows vs linux, ext4 vs fat32), and with git config filemode set to true which is default, it will become a modified file, which can happen many times between users and the server.

If the above commits were made at the same period, or some people commit this file, while others ignore this file as untracked or modified, git conflict can be produced.

@vinzid
Sorry so slow reply & thank you for your contribution :)

@yoshinorin That's all right, it's my pleasure. :)