Add developer name to appdata file

[MoralCode]

Similarly to #2152, this is a simple metadata update to help make the linter in the flatpak repo happy (see: flathub/no.mifi.losslesscut#66 for info)

wasnt exactly sure what to set the id to so i just used no.mifi

Developer name is a required item apparently: https://docs.flathub.org/docs/for-app-authors/metainfo-guidelines/#developer-name

also it seems like *.appdata.xml is no longer the current recommended filename for metadata: https://docs.flathub.org/docs/for-app-authors/metainfo-guidelines/#path-and-filename (but that's another issue for another time)

Summary by CodeRabbit

• New Features
  • Introduced a new developer section in the app's metadata, including the developer's name and ID.

[coderabbitai]

Walkthrough

The changes introduced in this pull request involve the addition of a <developer> element to the no.mifi.losslesscut.appdata.xml file. This element specifies the developer's ID and name, enhancing the metadata associated with the application. The overall structure and existing information within the file remain intact.

Changes

File	Change Summary
no.mifi.losslesscut.appdata.xml	Added <developer id="no.mifi"> and nested <name>Mikael Finstad</name> elements.

Possibly related PRs

• Fix metadata so that linter is happy and flatpak builds can resume #2152: This PR modifies the same no.mifi.losslesscut.appdata.xml file, indicating a direct connection in terms of file changes, although it focuses on different metadata elements.

🐇 In the garden of code, we hop with glee,
A new developer's name, as bright as can be!
With Mikael Finstad, our project takes flight,
In XML's embrace, everything feels right.
So let's celebrate this change, my friend,
For in every line of code, there's magic to send! 🌟

---

Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between f3d2a93 and 4ecd34a.

Files selected for processing (1)

• no.mifi.losslesscut.appdata.xml (1 hunks)

Additional comments not posted (1)

no.mifi.losslesscut.appdata.xml (1)

4-6: LGTM!

The addition of the <developer> element with the id attribute and the nested <name> element is consistent with the Flathub metainfo guidelines. The chosen id value matches the <component> ID, indicating a consistent naming convention. The developer name is appropriately provided within the <name> element.

The changes enhance the metadata without modifying the existing functionality or introducing any syntax errors.

---

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.