feat(ci): Test tagging and release

manoelhc commented 3 months ago

Summary by CodeRabbit

New Features
- Introduced an automated release tagging system that triggers upon pull request merges, utilizing title keywords to determine version updates.
Chores
- Updated .gitignore to exclude .vscode files.
Documentation
- Enhanced GitHub Actions workflows documentation to include details on automated release tagging and conditional test executions.

coderabbitai[bot] commented 3 months ago

Walkthrough

The recent updates streamline version management and tagging through automated workflows triggered by pull requests, improving the release process. Testing workflows now include logic to handle draft pull requests, enhancing control over test execution. The .gitignore file has been updated to exclude .vscode settings, maintaining project cleanliness.

Changes

Files	Change Summary
`.github/workflows/auto-tagging.yaml`, `.github/workflows/test.yaml`	Automated version bumping, tagging, and release notes generation based on pull request events; added draft PR checks in testing workflows.
`.gitignore`	Updated to ignore `.vscode` directory.

Tips

### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit .` - `Generate unit testing code for this file.` - `Open a follow-up GitHub issue for this discussion.` - Files and specific lines of code (under the "Files changed" tab): Tag `@coderabbitai` in a new review comment at the desired location with your query. Examples: - `@coderabbitai generate unit testing code for this file.` - `@coderabbitai modularize this function.` - PR comments: Tag `@coderabbitai` in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples: - `@coderabbitai generate interesting stats about this repository and render them as a table.` - `@coderabbitai show all the console.log statements in this repository.` - `@coderabbitai read src/utils.ts and generate unit testing code.` - `@coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.` Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. ### CodeRabbit Commands (invoked as PR comments) - `@coderabbitai pause` to pause the reviews on a PR. - `@coderabbitai resume` to resume the paused reviews. - `@coderabbitai review` to trigger a review. This is useful when automatic reviews are disabled for the repository. - `@coderabbitai resolve` resolve all the CodeRabbit review comments. - `@coderabbitai help` to get help. Additionally, you can add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed. ### CodeRabbit Configration File (`.coderabbit.yaml`) - You can programmatically configure CodeRabbit by adding a `.coderabbit.yaml` file to the root of your repository. - Please see the [configuration documentation](https://docs.coderabbit.ai/guides/configure-coderabbit) for more information. - If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: `# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json` ### Documentation and Community - Visit our [Documentation](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](https://discord.com/invite/GsXnASn26c) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.

deepsource-io[bot] commented 3 months ago

Here's the code health analysis summary for commits 0f92d16..0b0f286. View details on DeepSource ↗.

Analysis Summary

Analyzer	Status	Summary	Link
Python	✅ Success		View Check ↗
Test coverage	✅ Success		View Check ↗

Code Coverage Report

Metric	Aggregate	Python
Branch Coverage	87.9%	87.9%
Condition Coverage	87.9%	87.9%
Composite Coverage	96.2%	96.2%
Line Coverage	97.5%	97.5%

💡 If you’re a repository administrator, you can configure the quality gates from the settings.

codecov[bot] commented 3 months ago

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 96.06%. Comparing base (0f92d16) to head (0b0f286).

Additional details and impacted files

```diff @@ Coverage Diff @@ ## main #41 +/- ## ======================================= Coverage 96.06% 96.06% ======================================= Files 10 10 Lines 407 407 Branches 33 33 ======================================= Hits 391 391 Misses 10 10 Partials 6 6 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

codacy-production[bot] commented 3 months ago

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation	Diff coverage
:white_check_mark: +0.00% (target: -1.00%)	:white_check_mark: ∅

Coverage variation details

| | Coverable lines | Covered lines | Coverage | | ------------- | ------------- | ------------- | ------------- | | Common ancestor commit (0f92d160e1ab4e5c36ee9662e9bfd7b88fd1e6f3) | 407 | 397 | 97.54% | | | Head commit (0b0f2869275b10443a3dd17b88b982aca3a681dd) | 407 (+0) | 397 (+0) | 97.54% (**+0.00%**) | **Coverage variation** is the difference between the coverage for the head and common ancestor commits of the pull request branch: ` - `

Diff coverage details

| | Coverable lines | Covered lines | Diff coverage | | ------------- | ------------- | ------------- | ------------- | | Pull request (#41) | 0 | 0 | **∅ (not applicable)** | **Diff coverage** is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: `/ * 100%`