feat: add workflow templates

[gatici]

Adding each job templates that can be used in any repository by providing input variables.
E2E tests are not included in this PR and it only includes the existing workflows.

[gatici]

This is still in-progress.

[ghislainbourgeois]

Looks good, I have some comments

[gab-arrobo]

Overall, it looks good to me.
Just in case do you have an example of how you are planning to use these GHAs in the different repositories? I am asking this because I was expecting to see something like this

      branch-name:
-        description: Name of the branch to checkout
-        required: false
-        type: string
-        default: ${{ github.ref }}
+        - ${{ input_branch }}

Also, my understanding was that the workflow call is done from the perspective of the "calling" repository (e.g., amf, smf, config5g, etc.). That is, do we need to pass the branch name that we need to take action on?

[gatici]

Overall, it looks good to me. Just in case do you have an example of how you are planning to use these GHAs in the different repositories? I am asking this because I was expecting to see something like this

      branch-name:
-        description: Name of the branch to checkout
-        required: false
-        type: string
-        default: ${{ github.ref }}
+        - ${{ input_branch }}

Also, my understanding was that the workflow call is done from the perspective of the "calling" repository (e.g., amf, smf, config5g, etc.). That is, do we need to pass the branch name that we need to take action on?

Hello Gabriel,

I used the shared workflows in this PR omec-project/amf#374 and they run successfully. Please have a look.

[gab-arrobo]

Overall, it looks very good. I added some comments for your review. Thanks!

[gab-arrobo]

Add end of line

Suggested change

	fi
	fi

[gab-arrobo]

Add end of line

Suggested change

	VERSION: ${{ steps.version-change.outputs.version }}
	VERSION: ${{ steps.version-change.outputs.version }}

[gab-arrobo]

I think we can remove this line because it just indicates the user who approved the "previous" PR

Suggested change

author: ${{ github.actor }} <${{ github.actor_id }}+${{ github.actor }}@users.noreply.github.com>

[gab-arrobo]

Why do you need these lines? The next task is taking care of that (add, commit and push)

Suggested change

	git config --global user.email "github-actions[bot]@users.noreply.github.com"
	git config --global user.name "GitHub Actions"
	git add VERSION && git commit -m "Update VERSION file to $NEW_VERSION" && git push

[gab-arrobo]

Does this have to use brackets or can it be a list such as below?

Suggested change

	workflows: ["Tag GitHub"]
	workflows:
	- "Tag GitHub"

[gab-arrobo]

Why do you need to pull the submodules? I do not think any repo has a submodule

Suggested change

submodules: true

[gab-arrobo]

Why do you need this step? We did not need it before

[gab-arrobo]

What about something like this

Suggested change

	workflows: ["Tag GitHub"]
	workflows:
	- "Tag GitHub"

[gab-arrobo]

Just in case, have you checked what we can do regarding the creation of release branches (branch name is different than the content of the version file)? For example, in the amf repo, branch rel-1.3 has VERSION file with content 1.4.0

[gab-arrobo]

Should I understand that the GitHub runners have, by default, the GitHub client (gh) installed? Additionally, I should understand that this cannot be in the same GHA (i.e., tag-github) and that is why it is in its own directory (actions), correct?

[gab-arrobo]

@gatici,
BTW, I think we also need to add a Dependabot to handle dependency updates for the GitHub Action, correct?