Switch repository URL for official ESPAsyncWebServer library to https://github.com/ESP32Async/ESPAsyncWebServer

[mathieucarbou]

This request is a URL change for a repository.

With @me-no-dev, we are merging into one org (https://github.com/ESP32Async) the official AsyncTCP library (https://github.com/me-no-dev/ESPAsyncWebServer) with the community maintained for at https://github.com/mathieucarbou/ESPAsyncWebServer.

Both repos have been merged into one: https://github.com/ESP32Async/ESPAsyncWebServer, which is now the official repo for the ESPAsyncWebServer library.

[github-actions]

Hi @mathieucarbou.
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]

Arduino Lint has suggestions for possible improvements to https://github.com/ESP32Async/ESPAsyncWebServer:

Linting library in ESPAsyncWebServer
INFO: No header file found matching library name (ESP_Async_WebServer.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)                                                                                                      
WARNING: library.properties name ESP Async WebServer contains spaces. Although supported, best practices is to not use  
         spaces.                                                                                                        
         See: https://arduino.github.io/arduino-cli/latest/library-specification/#libraryproperties-file-format         
         (Rule LP015)                                                                                                   

Linter results for project: 0 ERRORS, 1 WARNINGS

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

Linting sketch in ESPAsyncWebServer/examples/CaptivePortal

Linter results for project: no errors or warnings

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

Linting sketch in ESPAsyncWebServer/examples/Filters

Linter results for project: no errors or warnings

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

Linting sketch in ESPAsyncWebServer/examples/Issue162

Linter results for project: no errors or warnings

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

Linting sketch in ESPAsyncWebServer/examples/Issue85

Linter results for project: no errors or warnings

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

Linting sketch in ESPAsyncWebServer/examples/SSE_perftest

Linter results for project: no errors or warnings

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

Linting sketch in ESPAsyncWebServer/examples/SimpleServer

Linter results for project: no errors or warnings

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

Linting sketch in ESPAsyncWebServer/examples/StreamFiles

Linter results for project: no errors or warnings

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

Linter results for projects: 0 ERRORS, 1 WARNINGS

[per1234]

Hello @mathieucarbou. I am confirming your request.

Unlike submissions, this type of request is still handled manually. The Library Manager index maintainer occasionally comes through to clear all the outstanding requests. They will merge this pull request when it is done. You will get a notification from GitHub at that time.

After that, you can monitor the indexing of the library via its dedicated logs web page.
Information about that here:
https://github.com/arduino/library-registry/blob/main/FAQ.md#can-i-check-on-library-releases-being-added-to-library-manager

[mathieucarbou]

@per1234 : thanks! do I need to rebase at one point ? Or you will just re-apply the diff ?

[mathieucarbou]

@per1234 : thanks! do I need to rebase at one point ? Or you will just re-apply the diff ?

Just saw #5808... 😆 Thanks!

[per1234]

do I need to rebase at one point ?

That is not necessary. The index maintainer will rebase and resolve any merge conflicts at the time they merge the PR (they need to perform an operation on the database before the PR can be merged).