The job trigger was narrowed to push:tags a while back, but the
job-level 'if: github.ref == refs/heads/master' was left in place.
A tag push never has github.ref == refs/heads/master, so the two
conditions are mutually exclusive: the job trigger fires only on
tag pushes, while the guard only allows master-branch refs, meaning
the job has been silently skipped on every run since the trigger
was narrowed.
This is also the likely source of the recent Git LFS bandwidth/
storage overage: while the trigger was still push-to-master (pre-
narrowing), this job ran on nearly every commit and committed a
new QElectroTech.qch (LFS-tracked) each time, via the auto-generated
update-qch PR -- accumulating one LFS object version per run."
* added deb build CI/CD + setup gitignore on local build/ dir
* added exception for test on branch
* fix image selection
* added XML option to Doxyfile + artifact output
* updated doxygen version
* added ci for doxygen
* added diff + fix action directory
* remove working dir option
* switch to atest doxygen version
* added aterfact upload
* added deployment step in ci + doxygen theme
* separated setup and doxygen step
* added correct path for dox build
* switch to docker action
* return to binary package
* dummy commit for pages
* swithced to upload-pages-artifact
* fixed typo not fetching submodules + pointing to correct doxygen theme as changes to it are in repo
* separate deb build to ci/cd branch for future MR
* remove debug log
* changed location of generation of .qch file
* adding sync
* collapse sync in one file
* added auto MR CI
* using checkout to push
* added test to downloaded dir
* fix add path
* check if file is marked as modified
* added path info
* drop artifact method
* fix path
* removed checkout clearing the repo
* force to pass gitignore filter
* setting up git lfs
* Push updated QCH file
* removed branch testing
---------
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
fixed action error due to rebasing