Skip to content

Conversation

@BojanJurca
Copy link
Contributor

No description provided.

@github-actions
Copy link
Contributor

Hi @BojanJurca.
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 github-actions bot added the topic: modification Change existing list entry label Dec 12, 2025
@github-actions
Copy link
Contributor

A problem was found with your submission https://github.com/BojanJurca/Lightweight-Standard-Template-Library-STL-for-Arduino

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

@github-actions
Copy link
Contributor

A problem was found with your submission https://github.com/BojanJurca/cin-cout-for-Arduino

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

@github-actions
Copy link
Contributor

Thanks for your interest in contributing to the Arduino Library Manager index @BojanJurca
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

@github-actions github-actions bot requested a review from per1234 December 12, 2025 20:15
@github-actions github-actions bot removed the request for review from per1234 December 12, 2025 20:19
@github-actions
Copy link
Contributor

A problem was found with your submission https://github.com/BojanJurca/Lightweight-Standard-Template-Library-STL-for-Arduino

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

@github-actions
Copy link
Contributor

Hi @BojanJurca.
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
Copy link
Contributor

A problem was found with your submission https://github.com/BojanJurca/cin-cout-for-Arduino

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

@github-actions
Copy link
Contributor

Thanks for your interest in contributing to the Arduino Library Manager index @BojanJurca
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

@github-actions github-actions bot requested a review from per1234 December 12, 2025 20:20
@per1234 per1234 self-assigned this Dec 13, 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 @BojanJurca. Thanks for your interest in contributing to the Arduino Library Manager.

The problems reported by the bot is caused by the fact that your pull request is a mess. You will see the problem if you look at the diff you are proposing here:

https://github.com/arduino/library-registry/pull/7403/changes

The reason this happened is because you submitted this pull request from a branch of your fork repository that is outdated and out of sync compared to the main branch here in the arduino/library-registry repository.

In the future, make sure to always create a dedicated branch in your fork for each pull request. You should never make any commits directly to the main branch in your fork. The main branch should always match the main branch in this repository exactly. This way, you can use the main branch as the base for the branches you create for your pull requests. You can learn how to do that 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 main branch in your fork is in sync with the main branch in this repository before you make the branch for your pull request. You can learn how to sync your fork from the documentation here:

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

Please properly sync your branch so that your pull request only propses the addition of the single line for the URL of your library to the repositories.txt file. It must not propose any changes to the preexisting items in the file.

Doing that will trigger another run of the automated checks. 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 topic: URL change Change library repository URL and removed topic: modification Change existing list entry labels Dec 13, 2025
@BojanJurca BojanJurca closed this by deleting the head repository Dec 13, 2025
@per1234 per1234 added conclusion: duplicate Has already been submitted and removed status: changes requested Changes to PR are required before merge labels Dec 13, 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: URL change Change library repository URL

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants