Merge branch 'main' into sb-ogg-1

Author: mihai-tudor-oracle

.github/workflows/banned_file_changes_pr.yml

@@ -3,7 +3,7 @@ on:
   # pull_request:
   #   branches: [ "**/*" ]
   pull_request_target:
-  
+
 jobs:
   check_for_banned_file_changes:
     name: Look for unsupported (banned) file modifications on PRs
@@ -31,7 +31,7 @@ jobs:
           echo 'Changes to files in .github are not allowed.'
       - name: Comment if .github changed
         if: contains(steps.files.outputs.all_files_changed, '.github')
-        uses: mshick/add-pr-comment@v1
+        uses: oracle-devrel/add-pr-comment
         with:
           message: |
             :no_entry: **Banned Files Modified**
@@ -43,15 +43,15 @@ jobs:
           echo 'Changes to license_policy.yml are not allowed.'
       - name: Comment if license_policy.yml changed
         if: contains(steps.files.outputs.all_files_changed, '"license_policy.yml"')
-        uses: mshick/add-pr-comment@v1
+        uses: oracle-devrel/add-pr-comment
         with:
           message: |
             :no_entry: **Banned Files Modified**
             Changes to `license_policy.yml` are not permitted.  Please revert your changes and re-submit a new PR.  Simply changing the file back to its original state and re-committing won't work (you must revert the changes made to it).
           repo-token: ${{ secrets.GITHUB_TOKEN }}
       - name: Look for changes to repolinter.json
         if: contains(steps.files.outputs.all_files_changed, '"repolinter.json"')
-        uses: mshick/add-pr-comment@v1
+        uses: oracle-devrel/add-pr-comment
         with:
           message: |
             :no_entry: **Banned Files Modified**
@@ -63,7 +63,7 @@ jobs:
           echo 'Changes to repolinter.json are not allowed.'
       - name: Look for changes to sonar-project.properties
         if: contains(steps.files.outputs.all_files_changed, '"sonar-project.properties"')
-        uses: mshick/add-pr-comment@v1
+        uses: oracle-devrel/add-pr-comment
         with:
           message: |
             :no_entry: **Banned Files Modified**
@@ -76,4 +76,4 @@ jobs:
       - name: Fail on banned file changes
         if: contains(steps.files.outputs.all_files_changed, '.github') || contains(steps.files.outputs.all_files_changed, '"license_policy.yml"') || contains(steps.files.outputs.all_files_changed, '"repolinter.json"') || contains(steps.files.outputs.all_files_changed, '"sonar-project.properties"')
         run: |
-          exit 1
+          exit 1

.github/workflows/license_audit.yml

@@ -31,7 +31,7 @@ jobs:
         run: echo "${{ steps.analysis.outputs.unapproved_licenses }}"
       - name: Comment if analysis finds unapproved licenses
         if: steps.analysis.outputs.unapproved_licenses == 'true'
-        uses: mshick/add-pr-comment@v1
+        uses: oracle-devrel/add-pr-comment
         with:
           message: |
             :no_entry: **License Inspection**

.github/workflows/repolinter.yml

@@ -34,7 +34,7 @@ jobs:
           echo "Errored: ${{ steps.analysis.outputs.errored }}"
       - name: Comment if analysis finds missing disclaimer
         if: steps.analysis.outputs.disclaimer_found == 'false'
-        uses: mshick/add-pr-comment@v1
+        uses: oracle-devrel/add-pr-comment
         with:
           message: |
             :no_entry: **FAILURE: Missing Disclaimer**
@@ -47,34 +47,34 @@ jobs:
           repo-token: ${{ secrets.GITHUB_TOKEN }}
       - name: Comment if analysis finds missing readme
         if: steps.analysis.outputs.readme_file_found == 'false'
-        uses: mshick/add-pr-comment@v1
+        uses: oracle-devrel/add-pr-comment
         with:
           message: |
             :no_entry: **FAILURE: Missing README**
             The README file seems to be missing.  Please add it.
-            
+
             Details:
             ${{ steps.analysis.outputs.readme_file_details }}
           repo-token: ${{ secrets.GITHUB_TOKEN }}
       - name: Comment if analysis finds missing license
         if: steps.analysis.outputs.license_file_found == 'false'
-        uses: mshick/add-pr-comment@v1
+        uses: oracle-devrel/add-pr-comment
         with:
           message: |
             :no_entry: **FAILURE: Missing LICENSE**
             The LICENSE file seems to be missing.  Please add it.
-            
+
             Details:
             ${{ steps.analysis.outputs.license_file_details }}
           repo-token: ${{ secrets.GITHUB_TOKEN }}
       - name: Comment if analysis finds copyright notice missing
         if: steps.analysis.outputs.copyright_found == 'false'
-        uses: mshick/add-pr-comment@v1
+        uses: oracle-devrel/add-pr-comment
         with:
           message: |
             :warning: **WARNING: Missing Copyright Notice(s)**
             It's a good idea to have copyright notices at the top of each file.  It looks like at least one file was missing this (though it might be further down in the file - this might be a false-positive).
-            
+
             Details:
             ${{ steps.analysis.outputs.copyright_details }}
           repo-token: ${{ secrets.GITHUB_TOKEN }}

CONTRIBUTING.md

@@ -0,0 +1,55 @@
+# Contributing to this repository
+
+We welcome your contributions! There are multiple ways to contribute.
+
+## Opening issues
+
+For bugs or enhancement requests, please file a GitHub issue unless it's
+security related. When filing a bug remember that the better written the bug is,
+the more likely it is to be fixed. If you think you've found a security
+vulnerability, do not raise a GitHub issue and follow the instructions in our
+[security policy](./SECURITY.md).
+
+## Contributing code
+
+We welcome your code contributions. Before submitting code via a pull request,
+you will need to have signed the [Oracle Contributor Agreement][OCA] (OCA) and
+your commits need to include the following line using the name and e-mail
+address you used to sign the OCA:
+
+```text
+Signed-off-by: Your Name <[email protected]>
+```
+
+This can be automatically added to pull requests by committing with `--sign-off`
+or `-s`, e.g.
+
+```text
+git commit --signoff
+```
+
+Only pull requests from committers that can be verified as having signed the OCA
+can be accepted.
+
+## Pull request process
+
+1. Ensure there is an issue created to track and discuss the fix or enhancement
+   you intend to submit.
+1. Fork this repository.
+1. Create a branch in your fork to implement the changes. We recommend using
+   the issue number as part of your branch name, e.g. `1234-fixes`.
+1. Ensure that any documentation is updated with the changes that are required
+   by your change.
+1. Ensure that any samples are updated if the base image has been changed.
+1. Submit the pull request. *Do not leave the pull request blank*. Explain exactly
+   what your changes are meant to do and provide simple steps on how to validate.
+   your changes. Ensure that you reference the issue you created as well.
+1. We will assign the pull request to 2-3 people for review before it is merged.
+
+## Code of conduct
+
+Follow the [Golden Rule](https://en.wikipedia.org/wiki/Golden_Rule). If you'd
+like more specific guidelines, see the [Contributor Covenant Code of Conduct][COC].
+
+[OCA]: https://oca.opensource.oracle.com
+[COC]: https://www.contributor-covenant.org/version/1/4/code-of-conduct/