Go to the Update Addon page and login with your GitHub account.
If you are uploading an add-on that exceeds 50MB, you also need to login with an Apple ID.
Fill in the information about this add-on you are adding, changing, or removing.
After clicking the Submit button, two pop-up windows will appear. On its first pop-up, simply enter the title of the addon you submitted
The second pop-up window is optional. State the changes you made on the addon's update on this window. Simply click OK if it is an entirely new addon submitted
The page will then automatically create a PR for you once the two pop-up windows are successfully filled up.
If the pull request is not created, there might be an issue with with your fork of this repository. The root cause might be that the size of your fork of this repository is getting too large. You can reset your fork of the repository by deleting it. Before deleting it, ensure that you don't have any open pull requests.
Go to your fork of this repository in https://github.com/YOUR_GITHUB_USERNAME/celestia-addon-validator.git (replace YOUR_GITHUB_USERNAME with your GitHub user name) and navigate to Settings. Find "Delete this repository" down the page and follow the instructions.
Validation should only take a few minutes.
If validation fails, it will appear like this.
Click Details, and see where it goes wrong.
In this example, title is missing in submitting a new add-on. If it fails, Click Close pull request and start from the beginning.
In a successful validation, a summary will be displayed in details.
After it passes validation, a collaborator can merge this pull request. After the pull request is merged, more checks will be performed automatically and the add-on will be uploaded to celestia.mobi.
It may take up to about an hour after the pull request is merged for users to see the changes on celestia.mobi.