Oisd

[norbertjoni]

I am not sure if I am doing right, but I would like to pull this to the new branches named oisd.
New branch because oisd list works well with all alone.
This list prioritizes functionality over blocking.

[mrrfv]

Your current pull request is set to merge the commits into main.

I believe this doesn't need a new branch - creating one just for a new filter list could make development much harder and complicated. Could you instead make a PR (or change your current one) that just modifies cf_list_create.js to work with OISD lists and creates a script used for downloading the oisd big list? Then the GitHub Action can be manually modified by the user to use OISD lists.

[norbertjoni]

Yes probably be cleaner if I just close this and pull a new one.
Question:

    - name: Clone repository and switch to v1 branch
      run: |
        git clone https://github.com/mrrfv/cloudflare-gateway-pihole-scripts.git
        cd cloudflare-gateway-pihole-scripts
        git checkout v1

What's the reason to use v1 instead of main? I don't see any difference.

[mrrfv]

It's used for versioning - we don't want to break the GitHub Action for people that just set up CGPS on their GitHub account and forgot about it. Every time a big change is introduced that will certainly break the project for GitHub Actions users (like more secrets being required, or some setting to be manually reviewed), a new branch will be created. Small fixes, such as adding compatibility with OISD lists, should still be merged with v1.