Currently, the Dokka Documentation Build is triggered already on pull_requests to main branch, which consumes unnecessary CI/CD resources and potentially slows down the development process by queuing up builds that aren't immediately necessary. In addition, the documentation should always contain the main branch and not the documentation of branches for which there is only one PR
Solution
Configure the CI/CD pipeline to only trigger the Dokka Documentation Build when changes are pushed to the main branch.
Additional context
No response
Code of Conduct
[X] I agree to follow this project's Code of Conduct and Contributing Guidelines
Problem
Currently, the Dokka Documentation Build is triggered already on pull_requests to main branch, which consumes unnecessary CI/CD resources and potentially slows down the development process by queuing up builds that aren't immediately necessary. In addition, the documentation should always contain the main branch and not the documentation of branches for which there is only one PR
Solution
Configure the CI/CD pipeline to only trigger the Dokka Documentation Build when changes are pushed to the main branch.
Additional context
No response
Code of Conduct