A simple NLP library allows profiling datasets with one or more text columns. When given a dataset and a column name containing text data, NLP Profiler will return either high-level insights or low-level/granular statistical information about the text in that column.
Missing functionality
Automatic semantic release using CI/CD is currently not supported in our GitHub repository. This means that developers have to manually trigger the release process, which is time-consuming and prone to human error. Additionally, it can lead to delays in deploying new features or bug fixes to production environments.
Proposed feature
I propose implementing a feature that enables automatic semantic release using Continuous Integration/Continuous Deployment (CI/CD) pipelines. This feature would allow developers to define release workflows directly in the repository's configuration files (e.g., YAML files), specifying conditions under which a release should be triggered, such as merging code into specific branches or tagging commits with version numbers.
Fix: Pull Request must follow commitizen standards
Alternatives considered
One alternative is to continue relying on manual release processes or using external CI/CD tools outside of GitHub. However, these approaches are less integrated with the repository and may require additional setup and maintenance overhead.
Additional context
Implementing automatic code release using CI/CD would not only improve developer productivity but also enhance the overall reliability and stability of our software deployments. It aligns with modern software development practices and enables faster time-to-market for new features and updates. Additionally, it promotes a consistent and standardized release process across teams and projects within our organization.
Missing functionality Automatic semantic release using CI/CD is currently not supported in our GitHub repository. This means that developers have to manually trigger the release process, which is time-consuming and prone to human error. Additionally, it can lead to delays in deploying new features or bug fixes to production environments.
Proposed feature I propose implementing a feature that enables automatic semantic release using Continuous Integration/Continuous Deployment (CI/CD) pipelines. This feature would allow developers to define release workflows directly in the repository's configuration files (e.g., YAML files), specifying conditions under which a release should be triggered, such as merging code into specific branches or tagging commits with version numbers.
Reference
Alternatives considered One alternative is to continue relying on manual release processes or using external CI/CD tools outside of GitHub. However, these approaches are less integrated with the repository and may require additional setup and maintenance overhead.
Additional context Implementing automatic code release using CI/CD would not only improve developer productivity but also enhance the overall reliability and stability of our software deployments. It aligns with modern software development practices and enables faster time-to-market for new features and updates. Additionally, it promotes a consistent and standardized release process across teams and projects within our organization.