Skip to content

Conversation

@KITTEN2008
Copy link
Contributor

No description provided.

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

ERROR: Arduino Lint found errors with https://github.com/KITTEN2008/74HC573A:

Linting library in 74HC573A
ERROR: Path does not contain a valid Arduino library.                         
       See: https://arduino.github.io/arduino-cli/latest/library-specification
       (Rule LS001)                                                           
INFO: No header file found matching library name (74HC573A.h). Best practices are for primary header filename to match  
      library name.                                                                                                     
      See: https://arduino.github.io/arduino-cli/latest/library-specification/#libraryproperties-file-format            
      (Rule LS008)                                                                                                      

Linter results for project: 1 ERRORS, 0 WARNINGS

-------------------

Linting sketch in 74HC573A/examples/Basic

Linter results for project: no errors or warnings

-------------------

Linter results for projects: 1 ERRORS, 0 WARNINGS

@github-actions
Copy link
Contributor

Thanks for your interest in contributing to the Arduino Library Manager index @KITTEN2008
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 Dec 21, 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 .

@KITTEN2008 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.

What you must do instead is CAREFULLY read the information provided by the bot and then fix the problem. Once you do that, another round of automated checks will be triggered. You can repeat that process in a single pull request as many times as is needed to get it to a fully compliant state. Once your submission passes all the checks it will automatically be accepted by the bot.

You will never fix the problem by submitting the same non-compliant pull request multiple times. That will only waste your time and 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.


If you have any questions, concerns, or problems, you are welcome to write a clear and detailed description in a comment on the pull request thread. I'll be happy to provide assistance.

@per1234 per1234 closed this Dec 21, 2025
@per1234 per1234 added the conclusion: duplicate Has already been submitted label Dec 21, 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