Problem trying to publish library

Projects Libraries
1

I don't see any category mentioning the Arduino Library Manager. There should be one.

I'm following the same method I used previously to add a library to the Arduino Library Manager repositories.txt file, but it doesn't seem to be working. Something seems to be different. Previously after I created the pull request, I saw it in the list of pull requests at https://github.com/arduino/library-registry/pulls but this time I don't. Instead, the pull request seems to be local to my fork of the library-registry: https://github.com/tedtoal/library-registry/pull/1

I'm never seeing any action taken on it.

2

I moved your topic to an appropriate forum category @tedtoal.

In the future, please take some time to pick the forum category that best suits the subject of your topic. There is an "About the _____ category" topic at the top of each category that explains its purpose.

This is an important part of responsible forum usage, as explained in the "How to get the best out of this forum" guide. The guide contains a lot of other useful information. Please read it.

Thanks in advance for your cooperation.

3

You diagnosed the cause accurately. You must submit the pull request to Arduino's repository. You instead submitted the pull request to your own fork of the repository, where it will never be seen by the submission system that runs in Arduino's repository.

Please try again by following the instructions here very carefully:

https://github.com/arduino/library-registry#instructions

If you have any questions or problems, just let me know and I'll help you out.

4

Perl, as I said in the topic, I DID in fact spend CONSIDERABLE TIME looking for an appropriate category and could not find one. I'm sorry I didn't find it, I scrolled through all the categories looking. I didn't notice the category search button, unfortunately.

ted

5

That is EXACTLY the instructions I followed. To a tee. Previously when I followed them, if I'm not mistaken, the forked repository had no "tedtoal-patch-1" branch like this one has, but instead, had a main branch where I added the line to the file and submitted a pull request. So, I don't know what caused a patch branch to be created.

6

I also have a question about my fork. Previously, after adding a library, I deleted my fork. Then when I wanted to do a new library, I forked again. Is that the right way to do it?

7

Thanks for the clarification! I investigated and found this is caused by a bug in the GitHub website, as discussed here:

I submitted a formal report to GitHub. Until then, it will be necessary to use a modified version of the procedure for submitting libraries.

I'll provide instructions you can follow to do that:

  1. Click the following link:
    Sign in to GitHub · GitHub
    The "Create a new fork" page will open.

  2. Click the "Create fork" button in the "Create a new fork" page.
    A page that shows that the fork is in the process of being created will open.

  3. Wait for the "Forking" process to finish.
    The home page of your fork of the library-registry repository will open.

  4. Click on the file repositories.txt under the list of files you see in that page.
    The "library-registry/repositories.txt" page will open.

  5. Click the pencil icon ("Edit this file") at the right side of the toolbar in the "library-registry/repositories.txt" page.
    The repositories.txt file will open in the online editor.

  6. Add the library repository's URL to the list.
    :exclamation: This should be the URL of the repository home page. For example:
    https://github.com/arduino-libraries/Servo
    ⓘ You can add it at any position in the list you like (e.g., the top, the bottom, next to your other libraries).

  7. Click the "Commit changes..." button located near the top right corner of the page.
    The "Commit changes" dialog will open.

  8. Click the "Commit changes" button in the "Commit changes" dialog.
    The "library-registry/repositories.txt" page will open.

  9. Click the "library-registry" link at the top of the "library-registry/repositories.txt" page.
    The home page of your fork of the library-registry repository will open.

  10. You should see a banner on the page that says:

    This branch is 1 commit ahead of arduino:main.

    Click the "Contribute" link near the right side of that banner.
    A menu will open.

  11. Click the "Open pull request" button in the menu
    The "Open a pull request" page will open.

  12. Click the "Create pull request" button in the "Open a pull request" page.

Your submission pull request will now be correctly submitted to the Arduino Library Registry.

Please let me know if you have any questions or problems while following those instructions.

I'll update the documentation in the project readme as well. Thanks for bringing this to our attention!

8

Thanks! Procedure worked perfectly.

9

Yes, that is the best way to do it. It is not mandatory to delete your fork, and you can submit multiple pull requests from the same fork if you like (though the procedure is slightly different than the simplified one I provided above). However, once your pull request has been merged there really is no point in keeping the fork.

It is a good practice to get into the habit of always deleting forks from your account once they no longer serve a purpose. If you don't do that, you might end up with quite an accumulation of pointless forks under your GitHub account. These can make it difficult to find the repositories in your account that you are actually looking for.

Over the years, I have created thousands of forks for the sake of submitting pull requests to various repositories. If I had not been scrupulous about deleting each of them after the pull request was merged it would be a real mess in my account with the hundreds of necessary forks (I have 1413 of them currently) mixed in with the other thousands of forks that were no longer necessary!

You are welcome. Thank you for your contributions to the Arduino Library Manager!

Regards,
Per

10

This is now in progress:

11

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.