Add workflow templates for a common pattern.

[adnapibar]

Description

This change adds GitHub Action workflows templates for repositories under the opensearch-project organization. The purpose is to conform to a common pattern for using GitHub Actions for CI & CD.

Issues Resolved

opensearch-project/opensearch-build#116

Check List

• Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Signed-off-by: Rabi Panda pandarab@amazon.com

[dblock]

Let's add a GH action badge and enable dummy CI on this repo?

[dblock]

++ Did you enable this in your fork? Can we see some results?

[adnapibar]

++ Did you enable this in your fork? Can we see some results?

I ran one on the common-utils fork based on the workflow template https://github.com/adnapibar/common-utils/runs/3234294435?check_suite_focus=true

[dblock]

Nice.

Maybe the script should be called dco-signoff-check just to be super explicit? NBD

[adnapibar]

@dblock Thanks! Can you please merge it.

[dblock]

Enable GH actions on your fork for the .github repo, and show me that these workflows work? I think you should do #25 as part of this PR to make sure the workflows are actually function. (I am pretty sure this will fail if we enable it now because those scripts called gradlew.)

[adnapibar]

Enable GH actions on your fork for the .github repo, and show me that these workflows work? I think you should do #25 as part of this PR to make sure the workflows are actually function. (I am pretty sure this will fail if we enable it now because those scripts called gradlew.)

Added the DCO check workflow for this repo. Here is how it worked in my .github fork https://github.com/adnapibar/.github/runs/3267249808?check_suite_focus=true

Yes, this is not a Gradle based Java project so for these kind of projects we can remove those steps and only keep the DCO check. For all Gradle based Java project the template can be used as is e.g. here is the workflow on the common-utils fork - https://github.com/adnapibar/common-utils/runs/3267308452?check_suite_focus=true

[dblock]

I am a little worried about the proliferation of things like workflow-template, these are a little hard to discover and they aren't exactly templates. Furthermore we have both OpenSearch and OpenSearch Dashboards projects in this repo. What do you think about just merging these into an actually running CI/CD workflow, and either commenting out the parts that invoke scripts or making a comment such as "for example of an OpenSearch workflow, see [link]", "for an example of an OpenSearch Dashboards workflow, see [link]"?