GitHub Desktop: "This file is empty"

Question

The file naaclhlt2016.tex is not empty on the client or in the repository, however GitHub Desktop displays "This file is empty". What could explain this?

The file naaclhlt2016.tex is present on GitHub repository:

git status:

It creates conflict when I try to sync:

Solution 1

After discussion, if the change of the tex file is only in term of metadata (and not actual file content change, after a latex recompilation), the GitHub Desktop might be unable to display any change.

Since it detects no change even though the git status list this file, it falls back to a "this file is empty" message.

Solution 2

In addition to the @VonC response.

To dissmiss this alert

Git desktop

1. unselect all changed files

2. select only the "this file is empty" files

3. try to commit

4. Git will display a commit error, saying that you can't do that. After closing the modal, Git should delete the files from the changes list.

Comments

[VonC]

Is this a new file, not yet pushed?

[Franck Dernoncourt]

@VonC The file naaclhlt2016.tex is present on GitHub repository.

[VonC]

Is it present in a different path? Is there any case difference anywhere in the path or name?

[Franck Dernoncourt]

@VonC same path, same case.

[VonC]

What does a git status says, when using the command line?

[Franck Dernoncourt]

@VonC git status thinks naaclhlt2016.tex has changed. I added the screenshot in the question. It looks like naaclhlt2016.tex appears in the list of changed files each time I compile the latex document.

[VonC]

If that document is generated, maybe it should not be versioned at all.

[Franck Dernoncourt]

@VonC True, but compiling it shouldn't change it. Looking at the "date modified", you are right though. I guess that explains it.

[VonC]

That explains the modified status, but not "file is empty", unless GitHub Desktop is unable to display metadata changes, and consider it does not detect any file content change?

[Franck Dernoncourt]

@VonC I guess GitHub Desktop is unable to display metadata changes.

[VonC]

That might be a bug or at least a surprising "feature" to report to GitHub support, and see if they think it is the expected response.

[Franck Dernoncourt]

I will report, but first I will try to understand why compiling a tex file with Texmaker changes the “date modified” meta-information. I will let you know when I submit the report.

[VonC]

@FranckDernoncourt Did you get any feedback from gitHub support about this feature?

[Franck Dernoncourt]

Sorry, I forgot whether I had submitted a report. I have just submitted one. Thanks for the follow-up.

[Franck Dernoncourt]

"That may not be the intended behavior, but I am not sure. I have shared your feedback with our team for them to consider."

[VonC]

@FranckDernoncourt the suspense is killing me ;)

[Varaquilex]

Any news on this?

[VonC]

@Varaquilex not on my side. Maybe the OP has more.

[Shai Petel]

I'd say this is the "solution" to this strange issue. Indeed trying to commit only these files results in an error, the commit is not done and the problem is gone. Thanks!