The activestate.yaml file acts as a shortcut to your project. The file includes project details such as its location online, language and package information, and security features. As such, it can be customized to meet the needs of your organization and shared across your teams to include proprietary code in your runtimes, add private scripts, and more.
activestate.yaml fileIf you wish to share an activestate.yaml file with your team, create a git repository and save your activestate.yaml to that repository. Share that git repository with your team through your regular channels.
To use the project associated with a given activestate.yaml file, simply open the correct directory and run state use <orgName>/<projectName> as you would normally after checking out a project from ActiveState.
A “Git project mismatch” warning occurs when the project field in your activestate.yaml does not match the project you are activating. The most common cause of this warning is when activating a forked project where the original project has an associated git repository with an activestate.yaml in it.
After confirming that the project field matches, you may need to run activate your project again by running state activate <org/project>.