Update gateway context after a Git checkout modifications

I am using version 8.3.3 and Git for change traceability.

When I reject modifications (git checkout ) to a code.py file and its associated resource.json (this also applies to views, named queries, etc.), and then execute a “Scan File System,” the gateway does not pick up the changes.

If I restart a Designer, the rejected script is still shown as modified.The only way to force the changes to be taken into account is to restart the service.

Is there an additional step I might be missing in my workflow?

There are two different scan requests. One for project content, and one for global content. Which scan endpoint (or WebUI button) are you using?

I am using the “Scan File System” from the Gateway Web UI (Platform section), not from the Designer.

I wasn't talking about the designer. There are two different scan buttons in the WebUI.

:see_no_evil_monkey:For the average user who isn’t yet familiar with this workflow.

I didn’t realize that the “Scan File System” button behaves differently depending on whether it’s used from the "Overview" page or the "Projects" page.
Now that I understand this, it makes much more sense.

Unfortunately, I haven’t had time to go through all the documentation since the changes from version 7.9 to the current versions.

Version and Source Control Guide | Ignition User Manual

Thanks, @pturmel