ci: Run CI on pushes to all branches

[jajik]

It's imho better to find potential issues before creating a PR. And development in the main branch is not ideal (definitely not for any bigger changes...)

[rpelisse]

@guidograzioli What's your feeling about this PR?

[guidograzioli]

We create PRs from forks, not branches, so I do not see real value in this change tbh

[jajik]

We create PRs from forks, not branches, so I do not see real value in this change tbh

Of course, that's not the point. The current setup forces contributors to develop in main in case they want to run CI before creating a PR, or to modify their ci.yml which is annoying with regard to synchronization.

[jajik]

I've just added another commit that prevents running the Documentation job in forks because it does not work there.

edit: See that the referenced action expects the repository contains tags, which does not have to be true.
edit2: e.g. https://github.com/jajik/jws-ansible-collection/actions/runs/11853814361/job/33034679384

[jajik]

We create PRs from forks, not branches, so I do not see real value in this change tbh

@guidograzioli Could you look at the proposed change again? As I tried to explain, it's especially useful in forks because the ci.yml gets used there as well. Currently, you're preventing people from running CI in their forks unless they're developing in main or they change the ci.yml. Both of these make rebasing more annoying than necessary. The advantage seems obvious, e.g., people open PRs with changes that actually work in CI...

[jajik]

^^ @guidograzioli @rpelisse

[jajik]

rebase & ping

[jajik]

I've just added another commit that prevents running the Documentation job in forks because it does not work there.

edit: See that the referenced action expects the repository contains tags, which does not have to be true. edit2: e.g. https://github.com/jajik/jws-ansible-collection/actions/runs/11853814361/job/33034679384

Dropping this as it's now part of #291.

Second look on this PR is still welcomed though.

[jajik]

@RanabirChakraborty any update on this?