fix!: remove screenshot intent

[JarbasAl]

details here OpenVoiceOS/ovos-gui-plugin-shell-companion#48

https://github.com/OVOSHatchery/ovos-skill-screenshots

Summary by CodeRabbit

Release Notes

• Bug Fixes

  • Removed functionality for taking screenshots across multiple languages, including English, Spanish, French, German, and more.

• Chores

  • Deleted the synchronization script for translation files and related metadata, streamlining the codebase.
  • Removed unnecessary imports and event handlers related to screenshot functionality.
  • Eliminated metadata files and intent definitions for screenshot commands in multiple languages.

These changes simplify the application by removing the screenshot feature and its associated commands in various languages, enhancing overall performance and maintainability.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The changes in this pull request involve the removal of a GitHub Actions workflow and several files related to taking screenshots across multiple languages. The deleted workflow, .github/workflows/sync_tx.yml, was designed to synchronize translations but has been eliminated. Additionally, multiple intent files for different languages, which contained commands for taking screenshots, have been deleted, along with associated code in __init__.py and other scripts. This results in the removal of screenshot functionality from the application.

Changes

File Path	Change Summary
.github/workflows/sync_tx.yml	Workflow removed: Run script on merge to dev by gitlocalize-app.
__init__.py	Removed methods: take_screenshot and screenshot_taken. Unused imports removed.
locale/*/take.screenshot.intent	Files deleted for multiple locales (ca-es, da-dk, de-de, en-us, es-es, fr-fr, it-it, nl-nl, pt-pt). Each contained phrases related to taking screenshots.
res/desktop/skill.json	Metadata file for skill removed.
scripts/sync_translations.py	Script for synchronizing translation files deleted.
translations/*/intents.json	Intent files deleted for multiple locales (ca-es, da-dk, de-de, en-us, es-es, fr-fr, it-it, nl-nl, pt-pt). Each defined intents for taking screenshots.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant App

    User->>App: Request to take a screenshot
    App-->>User: Screenshot functionality not available

Loading

🐰 "Oh, the scripts have hopped away,
No more screenshots to save the day!
With intents now lost in the mist,
We’ll find new ways to coexist.
A simpler code, a lighter load,
Onward we bound, down a new road!" 🐇✨

Warning

Rate limit exceeded

@github-actions[bot] has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 19 minutes and 33 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 4385a0e and 9d6f01c.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @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.
  • @coderabbitai help me debug CodeRabbit configuration file.

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 using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration 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 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 for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.