Separate repo for each action and workflow

[Gipphe]

Ref: #4 (comment)

Should we separate each action and workflow into their own repos? This is how actions seem to be managed by other parties, such as Github, Azure, Docker etc.

Pros for doing this:

• Each action and workflow can be versioned separately with tags.
• Actions and workflows can depend on specific versions of each other, instead of having to depend on the latest version.
• "Everyone else does it"

Cons:

• More setup in cloud-projects.
• No centralized space to discuss action/workflow issues
  • Can be solved in a similar manner to engineering-issues, whereby we have a dedicated repo for general action and workflow issues.

[Gipphe]

https://github.com/coopnorge/cloud-projects/pull/74
Draft setup for adding invididual repos.

[aucampia]

@AtzeDeVries I think we somehow settled on this, can we close this?

[AtzeDeVries]

Yes please

[nhhagen]

We are doing this