Skip to content

Conversation

@tailspb
Copy link
Contributor

@tailspb tailspb commented Oct 31, 2025

No description provided.

@github-actions github-actions bot added the topic: submission Add library to the list label Oct 31, 2025
@github-actions
Copy link
Contributor

A problem was found with your submission https://github.com/tailspb/tec02xx/tree/main/Arduino/Tec02XX

ERROR: Submission URL is not a Git clone URL (e.g., https://github.com/arduino-libraries/Servo).

@github-actions
Copy link
Contributor

Thanks for your interest in contributing to the Arduino Library Manager index @tailspb
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 per1234 self-assigned this Oct 31, 2025
Copy link
Contributor

@per1234 per1234 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hello @tailspb. Thanks for your interest in contributing to the Arduino Library Manager.

I see the bot reported a problem with your submission that will block its acceptance:

A problem was found with your submission https://github.com/tailspb/tec02xx/tree/main/Arduino/Tec02XX

❌ ERROR: Submission URL is not a Git clone URL (e.g., https://github.com/arduino-libraries/Servo).

It is mandatory that the library be located in the root of the repository. We do not allow libraries that are located in a subfolder of the repository, as is the case with your repository.

Please fix the problem so we can proceed with your submission.

There are two options for bringing the library into compliance with the requirements for inclusion in Library Manager:

Move library to root of repo

The library can be brought into compliance by moving all files and folders up two folder levels from the current location under the Arduino/Tec02XX subfolder of the repository to the root of the repository.

The correct structure will have the library.properties file in the root of the repository.

You can create a folder named extras and move all the non-library content under that folder:

https://arduino.github.io/arduino-cli/latest/library-specification/#extra-documentation

If you chose this approach, the following actions will be needed:

  1. Move the library to the root of the repository.
  2. Create a new release or tag in the library repository.
  3. Add a comment here in the pull request thread that mentions @ArduinoBot.

Dedicated repo

Alternatively, you can move the library to a new dedicated repository.

You may find this to actually facilitate the maintenance of the library since all activity in the library repo will be exclusively scoped to the library codebase, while the activity in the other repo will be exclusively scoped to the other components of the project.

GitHub offers unlimited free repositories, so there is no downside to creating additional repositories as far as your GitHub account is concerned.

If you chose this approach, the following actions will be needed:

  1. Move the library to the new repository.
  2. Update your pull request to add the URL of the dedicated library repository.

After that, the automated checks will run again. Once those are passing, your library will be automatically added to Library Manager.

If you have any questions or concerns, please let me know.

Regards, Per

@per1234 per1234 added status: changes requested Changes to PR are required before merge status: waiting for information More information must be provided before work can proceed labels Oct 31, 2025
Copy link
Contributor

@per1234 per1234 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Closing as duplicate of #7198.

@tailspb in the future please only create one pull request for each submission.

As was already clearly explained in the comments from the bot, there is no need or point in submitting a new pull request after a problem is detected with your existing PR.

Duplicate pull requests waste the time of the humans who maintain this free open source project.

⚠ Repeated irresponsible behavior may result in the revocation of your Library Manager Registry privileges.

Thanks in advance for your cooperation.

@per1234 per1234 closed this Oct 31, 2025
@per1234 per1234 added conclusion: duplicate Has already been submitted and removed status: waiting for information More information must be provided before work can proceed status: changes requested Changes to PR are required before merge labels Oct 31, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

conclusion: duplicate Has already been submitted topic: submission Add library to the list

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants