delete Yfrobot-FPM383-Library

[YFROBOTZL]

delete Yfrobot-FPM383-Library

[github-actions]

Hi @YFROBOTZL.
Your pull request has been detected as something other than a Library Manager submission.
A maintainer will need to review it before it can be merged.

If you intended to submit a library, please check the instructions and update your pull request if necessary:
https://github.com/arduino/library-registry/blob/main/README.md#instructions

[github-actions]

A problem was found with your submission https://github.com/YFROBOT-TM/Yfrobot-FPSensor-Library

❌ ERROR: Submission URL is already in the Library Manager index.

[github-actions]

Thanks for your interest in contributing to the Arduino Library Manager index @YFROBOTZL
Please resolve the error(s) mentioned in the previous comment.

After resolving the issue, trigger this check again by doing one of the following:

• Commit the required change to the branch you submitted this pull request from.
• Comment here, mentioning @ArduinoBot in the comment.

❗ NOTE: It is not necessary to open a new pull request. ❗

More information:
https://github.com/arduino/library-registry/blob/main/README.md#if-the-problem-is-with-the-pull-request

[per1234]

@YFROBOTZL your pull request contains two changes:

Addition of https://github.com/YFROBOT-TM/Yfrobot-FPSensor-Library to the list: 313596a (#6076)

Removal of https://github.com/YFROBOT-TM/Yfrobot-FPM383-Library from the list: 5cd877c (#6076)

The removal is valid and we will be happy to accommodate your request. However, the addition is no valid because you already added that repository (#6074). So we cannot proceed with your removal request until you have corrected the pull request so that it only proposes the removal of https://github.com/YFROBOT-TM/Yfrobot-FPM383-Library.

Please fix this problem.

---

Make sure to always create a dedicated branch in your fork repository for each pull request. You should never make any commits directly in the default branch (i.e., main) in your fork. The revision history of the default branch in your fork should always match the default branch in this repository exactly. This way, you can use the default branch as the base for the branches you create for your pull requests. Your use of the default branch in your repository for this pull request is the cause of these unnecessary problems.

You can learn how to correctly use branches for pull requests from this tutorial:

https://docs.github.com/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork

Always make sure the default branch in your fork is in sync with the default branch in this repository before you create a branch for a pull request. You can learn how to sync the branch in your fork from the documentation here:

https://docs.github.com/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork