chore: resolve PR comments

Author: TasoOneAsia

.github/CODEOWNERS

@@ -2,4 +2,4 @@
 # Main global owner #
 #####################
 
-*
+*

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -16,7 +16,6 @@ body:
         **Note:** If you are seeking community support or have a question, please consider starting a new thread via [GitHub discussions][discussions] or the [NGINX Community forum][forum].
 
         [issue search]: https://github.com/nginx/nginx-s3-gateway/issues
-
         [discussions]: https://github.com/nginx/nginx-s3-gateway/discussions
         [forum]: https://community.nginx.org
 
@@ -53,13 +52,13 @@ body:
       label: Environment Details
       description: Please provide details about your environment.
       value: |
-        - Version of the S3 container used (when downloaded from either Docker Hub or the GitHub Container Registry)
-        - Version of this project or specific commit when building your own S3 container
-        - Version of NGINX Open Source or NGINX Plus (OSS/Plus)
-        - Version of NGINX JavaScript
-        - Target deployment platform for the S3 container
-        - S3 backend implementation (AWS, Ceph, NetApp StorageGrid, etc...)
-        - Authentication method (IAM, IAM with Fargate, IAM with K8S, AWS Credentials, etc...)
+        - Version of the S3 container used (DockerHub/GCR):
+        - Commit/Tag (If Building from Source):
+        - Version of NGINX Open Source or NGINX Plus: [OSS/Plus]
+        - Version of NGINX JavaScript:
+        - Target deployment platforms [e.g. AWS/GCP/local cluster/etc...]:
+        - S3 backend implementation: [e.g. AWS, Ceph, NetApp StorageGrid, etc...]
+        - Authentication method: [IAM, IAM with Fargate, IAM with K8S, AWS Credentials, etc...]
     validations:
       required: true
 

.github/ISSUE_TEMPLATE/config.yml

@@ -9,4 +9,4 @@ contact_links:
     about: NGINX follows the Contributor Covenant Code of Conduct to ensure a safe and inclusive community
   - name: 💼 For commercial & enterprise users
     url: https://www.f5.com/products/nginx
-    about: F5 offers a wide range of NGINX products for commercial & enterprise users
+    about: F5 offers a wide range of NGINX products for commercial & enterprise users

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -14,7 +14,6 @@ body:
         **Note:** If you are seeking community support or have a question, please consider starting a new thread via [GitHub discussions][discussions] or the [NGINX Community forum][forum].
 
         [issue search]: https://github.com/nginx/nginx-s3-gateway/issues
-
         [discussions]: https://github.com/nginx/nginx-s3-gateway/discussions
         [forum]: https://community.nginx.org
 

.github/pull_request_template.md

@@ -7,7 +7,7 @@ Describe the use case and detail of the change. If this PR addresses an issue on
 Before creating a pull request (PR), run through this checklist and mark each as complete:
 
 - [ ] I have read the [contributing guidelines](/CONTRIBUTING.md).
-- [ ] I have signed the [F5 Contributor License Agreement (CLA)](https://github.com/f5/.github/blob/main/CLA/cla-markdown.md).
+- [ ] I have signed the [F5 Contributor License Agreement (CLA)](https://github.com/f5/f5-cla/blob/main/docs/f5_cla.md).
 - [ ] The PR title follows the [Conventional Commits specification](https://www.conventionalcommits.org/en/v1.0.0/).
 - [ ] If applicable, I have added tests that prove my fix is effective or that my feature works.
 - [ ] If applicable, I have checked that any relevant tests pass after adding my changes.

.github/workflows/f5-cla.yml renamed to .github/workflows/f5_cla.yml

@@ -2,9 +2,9 @@
 name: F5 CLA
 on:
   issue_comment:
-    types: [ created ]
+    types: [created]
   pull_request_target:
-    types: [ opened, closed, synchronize ]
+    types: [opened, closed, synchronize]
 permissions: read-all
 jobs:
   f5-cla:

.github/workflows/ossf-scorecard.yml renamed to .github/workflows/ossf_scorecard.yml

@@ -8,27 +8,19 @@ on:
   schedule:
     - cron: "0 0 * * 1"
   push:
-    branches: [main, master]
+    branches: [main]
   workflow_dispatch:
 # Declare default permissions as read only.
 permissions: read-all
 jobs:
   analysis:
     name: Scorecard analysis
     runs-on: ubuntu-24.04
-    # Delete the conditional below if you are using the OSSF Scorecard on a private repository.
-    if: ${{ github.event.repository.private == false }}
     permissions:
       # Needed if using Code Scanning alerts.
       security-events: write
       # Needed for GitHub OIDC token if publish_results is true.
       id-token: write
-      # Uncomment the permissions below if you are using the OSSF Scorecard on a private repository.
-      # contents: read
-      # actions: read
-      # issues: read # To allow GraphQL ListCommits to work
-      # pull-requests: read # To allow GraphQL ListCommits to work
-      # checks: read # To detect SAST tools
     steps:
       - name: Check out the codebase
         uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
@@ -40,10 +32,6 @@ jobs:
         with:
           results_file: results.sarif
           results_format: sarif
-          # (Optional) fine-grained personal access token. Uncomment the `repo_token` line below if you want to enable the Branch-Protection or Webhooks check on a *private* repository.
-          # To create the PAT, follow the steps in https://github.com/ossf/scorecard-action#authentication-with-fine-grained-pat-optional.
-          # repo_token: ${{ secrets.SCORECARD_TOKEN }}
-
           # Publish the results for public repositories to enable scorecard badges. For more details, see https://github.com/ossf/scorecard-action#publishing-results.
           # For private repositories, `publish_results` will automatically be set to `false`, regardless of the value entered here.
           publish_results: true

README.md

@@ -2,6 +2,8 @@
 [![OpenSSF Scorecard](https://api.securityscorecards.dev/projects/github.com/nginxinc/nginx-s3-gateway/badge)](https://securityscorecards.dev/viewer/?uri=github.com/nginxinc/nginx-s3-gateway)
 [![Project Status: Active – The project has reached a stable, usable state and is being actively developed.](https://www.repostatus.org/badges/latest/active.svg)](https://www.repostatus.org/#active)
 [![Community Support](https://badgen.net/badge/support/community/cyan?icon=awesome)](/SUPPORT.md)
+[![Community Forum](https://img.shields.io/badge/community-forum-009639?logo=discourse&link=https%3A%2F%2Fcommunity.nginx.org)](https://community.nginx.org)
+[![License](https://img.shields.io/badge/License-Apache%202.0-blue.svg)](https://opensource.org/license/apache-2-0)
 [![Contributor Covenant](https://img.shields.io/badge/Contributor%20Covenant-2.1-4baaaa.svg)](/CODE_OF_CONDUCT.md)
 
 # NGINX S3 Gateway
@@ -103,4 +105,4 @@ Please see the [contributing guide](/CONTRIBUTING.md) for guidelines on how to b
 
 [Apache License, Version 2.0](/LICENSE)
 
-© [F5, Inc.](https://www.f5.com/) 2020 - 2024
+© [F5, Inc.](https://www.f5.com/) 2020 - 2025

SUPPORT.md

@@ -36,10 +36,6 @@ at <https://mailman.nginx.org/mailman3/lists/>!
 Please see the [contributing guide](/CONTRIBUTING.md) or the [Getting Started](/README.md#getting-started) guide, for
 guidelines on how to best contribute to this project.
 
-<!-- ## Commercial Support
-
-Commercial support for this project may be available. Please get in touch with [NGINX sales](https://www.f5.com/products/get-f5/) or check your contract details for more information! -->
-
 ## Community Support
 
 This project does **not** offer commercial support. Community support is offered on a best effort basis through either