What does the different color text mean?


(Gene Clark) #1

So I was looking at he list of my Smart apps in the IDE and noticed that there are some written in different color text and was wondering what it means.


(Ricci Hoffer) #2

Black
Indicates that the file is unchanged between your forked GitHub repository and the IDE.
Green
Indicates that the file is in the IDE only, and not in any repository.
Blue
Indicates that the file exists in your GitHub repository, and has been modified in the IDE but not committed to the repository.
Magenta
Indicates that the file has been updated in the repository, but not in the IDE. To resolve this, you should click the Update from Repo button, where you sill see the file appear in the Obsolete column. More information about the Update from Repo button can be found below.
Red
Both the IDE version and repository version have been updated, and are in need of a conflict resolution. To resolve this, you should click the Update from Repo button and follow the steps there (more information about the Update from Repo action can be found below).
Brown
Indicates that the SmartApp or Device Type is unattached to the repository version. Typically this happens when a new SmartApp or Device Type is created from a template, and the name or namespace hasn’t been changed. If you update from the repo without changing the name or namespace, the IDE version will be replaced with the repo version. Typically in this case you would change the name and namespace to be unique for your code.


(David Lounsbury) #3

The colors indicate whether your instance of the DH or SA code is up-to-date with respect to the published state on github. The meaning of the colors is described in the github integration section of the developer docs, but basically you want them to be black, which indicates the code is up-to-date, or green, which indicates code that is not linked to GitHub.