Trigger CI on every push

[randombenj]

Requirements

All new code should be covered with tests, documentation should be updated. CI should pass.

Description of the Change

Triggers the CI build/test on every push (#1010 (comment)) as suggested by @ximon18

Checklist

• unit-test added (if change is algorithm)
• functional test added/updated (if change is functional)
• man page updated (if applicable)
• bash completion updated (if applicable)
• documentation updated
• author name in AUTHORS

[ximon18]

@randombenj: For some reason your "single" push triggered the workflow three times:

• here for commit 680e97a
• here for commit 4b40d77
• here for commit 7680b93

For the first two Git reports:

This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

I don't see anything in the documentation that explains this. However this may be why in the projects I have worked on the trigger for the push event was for pushes to the main branch only, and then also trigger on the pull_request event (either to any branch or just to main depending on the process used by the project).

Also note that one of the "benefits" (it can be confusing though) of triggering on the pull_request event is that the workflow is run as if the merge has already happened to the target branch, i.e. it tests against the result of merging the pull request, not against the code solely in the PR branch.

[lbolla]

FYI, I've rebased molior-rebase against master, so this PR will need rebase against the new molior-rebase, too.

[randombenj]

@ximon18 That's actually intended as I force pushed 2 times (and therefore the commit changed) :)

I would strongly suggest going for on: push as not only main and PRs are tested but every single push so you immediately notice when something breaks ;)

[randombenj]

@lbolla rebased the changes

[lbolla]

Builds for go 1.13 fail because of the "azure" library, which is using features from go 1.14+: https://pkg.go.dev/net/http#Header.Values

[lbolla]

1.17 fails. I've opened a separate ticket: #1012

EDIT: 1.16 fails with the same error. Ticket updated.

[randombenj]

@lbolla shall we reenable 1.17?