You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the local root directory, there is a file called Besprechung01.pdf -> The tool does not detect the files as an update of the remote file from the course. This is fine/desired behavior for now.
Now, I rename the file in the course to match the local file name: Besprechung01.pdf -> The tool does in fact display the local file as belonging to the remote file. (Aka it is displayed in the same line.)
At least for me, any local update of the file (e.g., changing the PDF file contents) did not result in the possibility of "activating" the update in the tool. The checkbox did not appear.
At this moment, I'm not sure if this use case is relevant to the tool in general. However, it was relevant for me to "pin" local files to already existing remote files.
The text was updated successfully, but these errors were encountered:
Consider the following scenario:
Besprechung01_.pdf
root
directory, there is a file calledBesprechung01.pdf
-> The tool does not detect the files as an update of the remote file from the course. This is fine/desired behavior for now.Besprechung01.pdf
-> The tool does in fact display the local file as belonging to the remote file. (Aka it is displayed in the same line.)At this moment, I'm not sure if this use case is relevant to the tool in general. However, it was relevant for me to "pin" local files to already existing remote files.
The text was updated successfully, but these errors were encountered: