Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merging repos, deploying filters to GitHub Pages #461

Open
scripthunter7 opened this issue Jun 20, 2024 · 0 comments
Open

Merging repos, deploying filters to GitHub Pages #461

scripthunter7 opened this issue Jun 20, 2024 · 0 comments
Labels
infrastructure Related to the repository infrastructure

Comments

@scripthunter7
Copy link
Member

scripthunter7 commented Jun 20, 2024

Note

Average users who use the built-in list of adblockers do not need to do anything with this change, it will happen automatically with the next update.
However, those who manually installed one of the lists should update the URL

We currently have two repositories:

According to my experience, this

  • complicates the management of issues and
  • often confuses users,

so we need to make 1 repo from this 2.

The plan is to delete the 'hufilter' repo and right after rename the 'hufilter-dev' repo back to 'hufilter', and the releases will happen on the gh-branch.

However, this also means changing the subscription URLs of the filters, so we have to be careful. So until the filter URLs change in all popular adblockers, I leave the two repository structure and just created a temporary deploy to the gh-pages branch in the 'hufilter' repo. This allows the old and new subscription URLs to work simultaneously during the transition period.

I also think it would be worthwhile to use jsDelivr instead of github.io URLs, for two reasons:

  1. jsDelivr is not affected if there is a temporary outage on GitHub
  2. jsDelivr also provides download statistics (this will not always be reliable, as e.g. AdGuard works through a filter registry, but it can give a reference number)

So the final URLs look like this:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
infrastructure Related to the repository infrastructure
Projects
None yet
Development

No branches or pull requests

1 participant