Add icon and logo for Aidot

[s1eedz]

Proposed change

Add icon and logo for Aidot

Type of change

• Add a new logo or icon for a new core integration
• Add a missing icon or logo for an existing core integration
• Add a new logo or icon for a custom integration (custom component)
  • I've added a link to my custom integration repository in the PR description
  • I've opened up a PR for my custom integration on the Home Assistant
    Python wheels repository
• Replace an existing icon or logo with a higher quality version
• Replace an existing icon or logo after a branding change
• Removing an icon or logo

Additional information

• This PR fixes or closes issue: fixes #
• Link to code base pull request: Add new integration for AiDot core#117337
• Link to documentation pull request:
• Link to integration documentation on our website:
• Link to custom integration repository:

Checklist

• The added/replaced image(s) are PNG
• Icon image size is 256x256px (icon.png)
• hDPI icon image size is 512x512px for (icon@2x.png)
• Logo image size has min 128px, but max 256px, on the shortest side (logo.png)
• hDPI logo image size has min 256px, but max 512px, on the shortest side (logo@2x.png)

[c0ffeeca7]

Thank you, @s1eedz 👍

[frenck]

@s1eedz Was there a reason for the merge? Was there a conflict? Did something change?

Not fully understanding the action here and the reasoning behind it.

../Frenck

[s1eedz]

@s1eedz Was there a reason for the merge? Was there a conflict? Did something change?

Not fully understanding the action here and the reasoning behind it.

../Frenck

@frenck This is a new integration for aidot. Main code link: home-assistant/core#117337. I don't see a conflict, is there something wrong? If so, thank you very much for your correction. I'll quickly revise my question here.

[frenck]

I don't know if something is wrong? That was my question for you...

You merged, and I was asking for the reasoning.

[s1eedz]

I don't know if something is wrong? That was my question for you...

You merged, and I was asking for the reasoning.

Sorry, I'm not familiar with the operation of github. I executed the update branch on github, but I didn't know that its default operation is merge, not rebase. What should I do now, should I close the PR and submit a new one? Or is there another way? Should I not execute update branch? I thought this would cause conflicts, so I operated this button.

[frenck]

I executed the update branch on github, but I didn't know that its default operation is merge, not rebase.

I know you did, the logs tells us. I didn't understand why and was asking about that. Was there something wrong? Why was it needed to merge the branch?

[s1eedz]

I executed the update branch on github, but I didn't know that its default operation is merge, not rebase.

I know you did, the logs tells us. I didn't understand why and was asking about that. Was there something wrong? Why was it needed to merge the branch?

I see that the branch is out-of-date，and then there's an update button, so I. . . .. . . .Maybe I can discard these merge commits through git operations, and I'll learn how to do that. . .this may take a while...

[frenck]

The PR was approved, you made changes by updating the branch. This causes the CI to require a new approval and uses CI resources to test/validate your PR again.

Normally, there is no need for this, unless there is a conflict or change (or weeks have passed).

Considering that, I assumed something has changed... if not, then please don't do that. Thanks 👍

../Frenck

[s1eedz]

unless

Thank you for telling this, I'm sorry for this.

[c0ffeeca7]

@s1eedz, what are you trying to do? Why did you close this PR now?