1. Proposed title of this feature request
Implement provider for syncing GitHub secrets via External Secrets Operator (ESO)

2. What is the nature and description of the request?
My customer stores secrets securely in GitHub organization secrets and wants to synchronize them into OpenShift (Kubernetes) Secrets for use by Operators and other processes running there, such as CSI drivers, SCM providers, and API callers.

A provider for GitHub Secrets is available today as documented here but it is WriteOnly as can be seen in the code today here: https://github.com/external-secrets/external-secrets/blob/10d9af756b3f503d4083a2cc8a18e53f2b16aca0/pkg/provider/github/provider.go#L49.

This request is to extend this provider to support Read operations from GitHub secrets as well. Thank you!

An equivalent request has been opened in the upstream External Secrets repo here.

3. Why does the customer need this? (List the business requirements here)
Customer wants to use GitHub secrets as a secure store for secrets and synchronize those with Kubernetes/OpenShift Secrets.

4. List any affected packages or components.
External Secrets Operator