# Using the Thin Client It's possible to use directly the [Thin Client](/the-client/client.md) in a GitHub workflow. You may however need to setup the environment in advance for specific languages, and you always need to have support for Java inside the workflow itself. For example if you want to scan a dotnet project you will probably need to use the actions/setup-dotnet to prepare it, while if you want to scan a Swift/Cocoapods project, you will need at least to to use macos as a base image. This also is useful when you want to use a very specific version of the tooling for the scan, as the GitHub action contains only one version for each toolset. A typical workflow would be something along those lines: * select the correct image ro run on * check out the project * if required, set up the tooling needed (you may need a specific version) * if required, set up JDK to run the Thin Client * download the Thin Client * run the Thin Client We created a set of lives examples for the most common cases: * [Java/Maven project](https://github.com/MeterianHQ/java-sample-project-cli/blob/master/.github/workflows/main.yml) * [Swift/Cocoapods project](https://github.com/MeterianHQ/swift-sample-project-cli/blob/master/.github/workflows/main.yml) * [Dotnet project](https://github.com/MeterianHQ/dotnet-sample-project-cli/blob/master/.github/workflows/main.yml) If you need other examples please get in touch with --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.meterian.io/online-integrations/meterian-scanner-github-action/using-the-thin-client.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.