@kapa.ai - Can you help me with how to resolve a couple of issues with my draft pull request. (https://github.com/airbytehq/airbyte/pull/73360) 1. Label - connectors/source/google-search-console - has been added but it is not relevant to my connector. This is my connector label connectors/source/tulip which has also been added - checks are failing because of this - how can i remove that label? 2. How do I set up the BYO credentials to all me to test my connector. The connector has passed all local testing and has been deployed end to end in a local airbyte docker deploy and fully tested end to end with a destination connector (snowflake). Currently failing Connector CI because of credentials missing

1. For the incorrect label: The knowledge sources don’t describe how labels are managed on GitHub issues/PRs, so I can’t give a repo‑specific procedure. In general, labels on Airbyte PRs are managed by maintainers and/or automation, and the docs only say that your PR should follow naming conventions and link to an issue, not how to change labels yourself. [[Astra DB PR process](https://discuss.airbyte.io/t/5415)] Because of that, the safest path (and the only one clearly supported by the docs) is: - Leave the correct connector label (

connectors/source/tulip

) as is. - Ask an Airbyte maintainer to remove the irrelevant

connectors/source/google-search-console

label: - Either as a PR comment, or - In the

#help-connector-development

Slack channel, referencing your PR URL. [[Astra DB PR process](https://discuss.airbyte.io/t/5415)] 2. For BYO credentials / missing CI credentials: From the docs, connector tests in CI (unit, integration, acceptance, regression) are run via

airbyte-ci connectors --name=<connector_name> test

and require credentials when integration or acceptance tests are enabled. [[Testing connectors](https://docs.airbyte.com/platform/connector-development/testing-connectors)] Credentials for CI are wired through: -

connectorTestSuitesOptions

in

metadata.yaml

, where each suite can declare

testSecrets

(name, secretStore, optional fileName). [[Connector metadata test suites](https://docs.airbyte.com/platform/connector-development/connector-metadata-file#the-connectortestsuitesoptions-section)] - Those

testSecrets

refer to secrets stored in Google Secret Manager (GSM) under Airbyte’s

airbyte-connector-testing-secret-store

. [[Connector metadata test suites](https://docs.airbyte.com/platform/connector-development/connector-metadata-file#the-connectortestsuitesoptions-section)] As a community contributor, you cannot directly add new CI secrets; the docs explicitly say this requires manual intervention from an Airbyter and you should coordinate with your PR reviewers: > “If you are a community contributor please note that addition of a new secret to our secret store requires manual intervention from an Airbyter. Please reach out to your PR reviewers if you want to add a test secret to our CI.” [[Connector metadata test suites](https://docs.airbyte.com/platform/connector-development/connector-metadata-file#the-connectortestsuitesoptions-section)] So, to get CI passing: 1. Ensure your

metadata.yaml

correctly declares the test suites you actually need (

unitTests

,

integrationTests

,

acceptanceTests

) and, if applicable, the

testSecrets

entry (name, GSM store, optional

fileName

like

config.json

). [[Connector metadata test suites](https://docs.airbyte.com/platform/connector-development/connector-metadata-file#the-connectortestsuitesoptions-section)] 2. In your PR description or comments, explicitly: - State that local tests and local Docker deployment are passing. - Point to the failing CI step and explain it’s due to missing test credentials. - Ask the reviewer/Airbyte engineer to: - Create the required GSM secret(s) for your connector, and - Wire them to CI according to the

metadata.yaml

definition. If you want to mirror the CI setup locally with your own GSM project (for your own testing), the docs describe how to store connector configs as JSON secrets in GSM and fetch them with

airbyte-cdk secrets

, but this is for your GCP project, not Airbyte’s CI. [[Managing secrets in GSM](https://docs.airbyte.com/platform/connector-development/local-connector-development#managing-connector-secrets-in-gsm)] In short: - You can’t reliably “fix” the wrong label or add CI credentials yourself; both require maintainer help. - Use PR comments and/or

#help-connector-development

Slack to: - Request removal of the

connectors/source/google-search-console

label. - Request creation/wiring of GSM test secrets for your connector as defined in

metadata.yaml

.