Make the new add-on template repo a link in the documentation#78
Merged
josephsl merged 1 commit intonvdaaddons:masterfrom Mar 17, 2026
Merged
Make the new add-on template repo a link in the documentation#78josephsl merged 1 commit intonvdaaddons:masterfrom
josephsl merged 1 commit intonvdaaddons:masterfrom
Conversation
Contributor
Author
|
Hi @josephsl. Would you mind merge this PR. It's in the old repo on purpose, to have a link to redirect to the new one. Thanks. |
Contributor
Author
|
Thanks Joseph! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue
The new official repo for add-on template is now hosted by nvaccess fork, not this one (nvdaaddons). This is mentioned on top of the readme of this repo what is a good thing.
Unfortunately, when searching for "NVDA add-on template", Google still directs us to the current old repo (nvdaaddons one).
Solution
For more efficiency, make the new repo mentioned in the readme a link, so that one can click it and go immediately to the new repo.