A CLI tool that generates changelogs from git repositories by extracting and enriching commit data.
Chyle is a command-line tool that generates changelogs by analyzing git repositories. It fetches commits based on configurable criteria, extracts data like commit messages and authors, and can enrich this data using external sources before publishing the results. It solves the problem of manually curating changelogs by automating the process and integrating with existing development workflows.
Development teams, DevOps engineers, and open-source maintainers who need automated, customizable changelog generation from git history.
Developers choose Chyle for its flexibility in data extraction and enrichment, modular pipeline design, and ease of configuration, allowing tailored changelogs without manual effort.
Changelog generator : use a git repository and various data sources and publish the result on external services
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Extracts data from commit messages, authors, and git metadata using customizable criteria, enabling detailed and tailored changelog entries as highlighted in the README's 'How it works' section.
Integrates with external APIs and shell commands to enhance commit payloads, allowing teams to add context like issue links or deployment status without manual curation.
Allows users to mix, skip, or combine processing steps such as fetching, enriching, and publishing, providing high customization for various workflows as described in the key features.
Includes a `config` command with prompts to quickly generate configuration files, reducing initial setup time and complexity for users new to the tool.
Requires detailed YAML configuration or generated files, which can be overwhelming for users seeking simple, out-of-the-box solutions, as noted in the setup dependency on manual config.
Effectiveness is heavily dependent on well-formatted commit messages; messy or inconsistent histories may produce inaccurate or incomplete changelogs, limiting automation benefits.
Lacks built-in connectors for popular project management tools like Jira or GitHub Issues, necessitating custom API setups for enrichment and publishing, adding to setup effort.
No graphical user interface or web-based dashboard, which may not suit teams preferring visual tools or automated reporting systems, as it's solely a command-line tool.