To run deadcode as a client-side tool:
Enable Run analysis through build server in your repository Settings, tab General, Repository analysis.
This setting enables Codacy to wait for the results of the local analysis before resuming the analysis of your commits.
Set up an API token to authenticate on Codacy:
If you're setting up one repository, obtain a project API token and set the following environment variable to specify your project API token:
export CODACY_PROJECT_TOKEN=<your project API token>
If you're setting up multiple repositories, obtain an account API Token and set the following environment variable to specify the account API token:
export CODACY_API_TOKEN=<your account API token>
Never write API tokens on your configuration files and keep your API tokens well protected, as they grant owner permissions to your projects on Codacy.
We recommend that you set API tokens as environment variables. Check the documentation of your CI/CD platform on how to do this.
If you're using Codacy Self-hosted set the following environment variable to specify your Codacy instance URL:
export CODACY_API_BASE_URL=<your Codacy instance URL>
Download and run the Codacy Analysis CLI on the root of the repository, specifying the tool deadcode.
codacy-analysis-cli analyze --tool deadcode \ --allow-network \ --upload \ --verbose
If you're using an account API token, you must also provide the flags
--project. You can obtain the values for these flags from the URL of your repository dashboard on Codacy:
codacy-analysis-cli analyze --provider <gh, ghe, gl, gle, bb, or bbe> \ --username <name of your Codacy organization> \ --project <name of your repository> \ --tool deadcode \ --allow-network \ --upload \ --verbose
The Codacy Analysis CLI runs deadcode on your repository and uploads the results to Codacy so you can use them in your workflow.
Did this page help you?
Thank you for the feedback!
We're sorry to hear that. Please let us know what we can improve.