feat: Add custom GitHub Actions to a separate repository

[fnesveda]

I was adding the usage of our custom GitHub Actions to a lot of repositories, and it felt confusing that actions live in a repository called workflows.

I've moved them to this new repository which will contain just actions, so that you can use them as it would make sense, e.g.:

  - name: Commit to a new branch
    uses: apify/actions/signed-commit@v1.0.0
    with:
      commit-message: "chore: add greeting"

I've also done some changes to simplify the setup:

• I've rewritten the execute-workflow action to use a composite action using github-script, so that it doesn't need to be compiled (since github-script can run TypeScript files natively)
• I've renamed the commit action to signed-commit to make it clearer why it's used just from the name

After this is merged, I will replace all the relevant usages of apify/workflows in other repositories with apify/actions and then delete the custom actions from the workflows repository.

[janbuchar]

This caught my eye:

* I've rewritten the `execute-workflow` action to use a composite action using `github-script`, so that it doesn't need to be compiled (since `github-script` can run TypeScript files natively)

...usually, you write typescript so that it can be checked, and I highly doubt that tsc --noEmit will search yaml files for inline typescript

[fnesveda]

This caught my eye:

* I've rewritten the ``execute-workflow`` action to use a composite action using ``github-script``, so that it doesn't need to be compiled (since ``github-script`` can run TypeScript files natively)

...usually, you write typescript so that it can be checked, and I highly doubt that tsc --noEmit will search yaml files for inline typescript

It won't, but the main logic of the action is in its own .ts file, so that it can be type-checked, the yaml file of the action contains just a thin wrapper around it.

[janbuchar]

This caught my eye:

* I've rewritten the ```execute-workflow````action to use a composite action using````github-script````, so that it doesn't need to be compiled (since````github-script``` can run TypeScript files natively)

...usually, you write typescript so that it can be checked, and I highly doubt that tsc --noEmit will search yaml files for inline typescript

It won't, but the main logic of the action is in its own .ts file, so that it can be type-checked, the yaml file of the action contains just a thin wrapper around it.

I see. I guess that should work. Oh, also there is one more custom action in apify/workflows#238 - could you add it here as well?

[fnesveda]

Oh, also there is one more custom action in apify/workflows#238 - could you add it here as well?

OK, added 👍

[vdusek]

Makes sense.

Just one question: do we want to use main or master? 😄 AFAIK, all our repos use master except apify/workflows, which uses main 🙈.

[fnesveda]

I think the old repos use master and most new repos use main, since main is the new default for a couple of years now 🙂 Since there is no consistency anymore, let's use main since it's the default now.

[vdusek]

I think the old repos use master and most new repos use main, since main is the new default for a couple of years now 🙂 Since there is no consistency anymore, let's use main since it's the default now.

Okay, just add that master is still the default branch name in git itself, default main is a GitHub thing.