workaround: publish docker image by pushing on development branch

[LizenzFass78851]

Description

This adds the variable components branch so that if github.ref_name is recognized as development, it also pushing the docker image to the development tag

Motivation and Context

In one of the last workflow runs that was triggered by pushing on the development branch, an error occurred that was triggered when the Docker image was built and not the development branch of FTL, Web and Core was loaded, but rather the respective master branch.
https://github.com/pi-hole/docker-pi-hole/actions/runs/18255584741/job/51976380837#step:10:399

How Has This Been Tested?

I tested the workflow with deviations in my fork with the changes

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.

[yubiuser]

Thanks for catching this. It fails, because it tries to add a file to the image that is not part of core's master branch yet.

I'm undecided yet regarding this PR. It will alter how we tag things. Currently, nightly contains development branch of all components and the docker repo. development uses the master branches of the components, but the development branch of this repo.
With this change, development will be like nightly

[PromoFaux]

That's a good point - the development tag should include all the actual released components (hence master branch override) and only include docker-specific dev changes. Of course, that's how we have ended up in this situation - the file structure of the core repo has changed in development, and has not yet been released to master.

One pottential workaround until such time as we can release is to add the following patch to this repo's development branch:

diff --git a/build.sh b/build.sh
old mode 100755
new mode 100644
diff --git a/src/Dockerfile b/src/Dockerfile
index cb7a061..49375e9 100644
--- a/src/Dockerfile
+++ b/src/Dockerfile
@@ -90,8 +90,12 @@ RUN cd /etc/.pihole && \
     install -Dm755 -d /var/log/pihole && \
     install -Dm755 -d /var/lib/logrotate && \
     install -Dm755 -t /usr/local/bin pihole && \
-    install -Dm644 ./advanced/bash-completion/pihole.bash /etc/bash_completion.d/pihole && \
-    install -Dm644 ./advanced/bash-completion/pihole-ftl.bash /etc/bash_completion.d/pihole-FTL && \
+    (if [ -f ./advanced/bash-completion/pihole.bash ]; then \
+        install -Dm644 ./advanced/bash-completion/pihole.bash /etc/bash_completion.d/pihole; \
+        install -Dm644 ./advanced/bash-completion/pihole-ftl.bash /etc/bash_completion.d/pihole-FTL; \
+    else \
+        install -Dm644 ./advanced/bash-completion/pihole /etc/bash_completion.d/pihole; \
+    fi) && \
     install -T -m 0755 ./advanced/Templates/pihole-FTL-prestart.sh /opt/pihole/pihole-FTL-prestart.sh && \
     install -T -m 0755 ./advanced/Templates/pihole-FTL-poststop.sh /opt/pihole/pihole-FTL-poststop.sh && \
     addgroup -S pihole -g ${PIHOLE_GID} && adduser -S pihole -G pihole -u ${PIHOLE_UID} && \

[LizenzFass78851]

I applied the patch and removed the change that was intended for the GitHub workflow.

[LizenzFass78851]

closed, as implementation is continued in pull request #1906