maxpeterkaya/changelog
Watch
1
0
Fork
You've already forked changelog
 0
Code Issues 1 Pull requests 2 Projects Releases 21 Packages 1 Wiki Activity Actions
Page: Troubleshooting
Pages
Home Inputs Reference Installation Outputs and Commit Groups Styles and LLM Providers Tag Ranges and Rollup Troubleshooting Writing Changelogs to the Repository
1 Troubleshooting
maxpeterkaya edited this page 2026-09-16 10:11:16 -04:00
Table of contents

Troubleshooting

Enable debug: "true" to get detailed logs when diagnosing a problem.

Configuration

No instance url provided! server_url is missing. Set it to your Forgejo base URL, for example https://vc.maxkaya.com.

Token not set! token is missing. Pass a token secret with read access to the repository and write access to releases and tags.

Unknown changelog style, using conventional style was set to a value other than conventional, detailed, or summary. The action uses conventional.

Changelog style requires an LLM provider, falling back to conventional style is detailed or summary but no provider is enabled. Enable Ollama or OpenAI, or use conventional. See Styles and LLM Providers.

No tags set at all! Using latest tag from repository... This is informational. No explicit tag inputs were provided, so the newest tag is used.

Tags and releases

latest tag not found The repository has no tags. Create at least one tag, then run again.

Latest tag exists but no previous tag found, creating changelog based on all commits. Expected when the repository has a single tag, such as a first release. The changelog covers all commits up to that tag.

Rollup base tag not found, falling back to previous tag Rollup could not find the base tag for the release series (for example v3.2.0 is not tagged). The action uses the previous tag instead. Create the base tag if you want the wider range. See Tag Ranges and Rollup.

Release not found, creating release... No release existed for the tag, so the action created one. This is normal for a new tag.

LLM providers

Ollama URL not set, disabling AI integration! or OpenAI URL not set, disabling AI integration! The provider was enabled without a URL. Set the matching *_url.

No Ollama API Key provided... Informational. Ollama runs without a key, and the action continues. Set ollama_key if your instance requires authentication.

No OpenAI model provided, disabling AI integration! openai_enabled is set but openai_model is empty. Set a model.

Truncation warnings A message such as Ollama response was truncated or OpenAI response was truncated means the model hit its output limit. Use a model with a larger output budget or fewer/larger commits per release.

Writing to the repository

Nothing is committed The generated content matches the existing file, so there was nothing to commit. This is expected on a re-run.

Push rejected or authentication failed The token lacks write access to the repository contents, or the workflow did not check out the repository. See Writing Changelogs to the Repository.

Wrong branch updated The action pushes to the branch input, then GITHUB_REF_NAME, then the current branch. Set branch explicitly if the default is not what you want.

Home · Installation · Inputs Reference · Outputs and Commit Groups · Tag Ranges and Rollup · Writing Changelogs to the Repository · Styles and LLM Providers