Git providers supporting CI

[nataliefiann]

What are you changing in this pull request and why?

I've created this PR with reference to this git issue: #3704 to help users clarify which Git providers support CI.

In the PR, I have updated the Continuous integration page, created a card on the Git configuaration page and linked the table I created in the CI doc to it. I also created and used a snippet from https://docs.getdbt.com/docs/deploy/ci-jobs#trigger-a-ci-job-with-the-api

Update - I've also added the snippet to the Import a project by git URL and Continuous integration jobs in dbt Cloud pages.

Closes: #3704

Checklist

• I have reviewed the Content style guide so my content adheres to these guidelines.
• The topic I'm writing about is for specific dbt version(s) and I have versioned it according to the version a whole page and/or version a block of content guidelines.
• I have added checklist item(s) to this list for anything anything that needs to happen before this PR is merged, such as "needs technical review" or "change base branch."
• The content in this PR requires a dbt release note, so I added one to the release notes page.

---

🚀 Deployment available! Here are the direct links to the updated files:

• https://docs-getdbt-com-git-nfiann-ci-and-git-dbt-labs.vercel.app/docs/cloud/git/git-configuration-in-dbt-cloud
• https://docs-getdbt-com-git-nfiann-ci-and-git-dbt-labs.vercel.app/docs/cloud/git/import-a-project-by-git-url
• https://docs-getdbt-com-git-nfiann-ci-and-git-dbt-labs.vercel.app/docs/deploy/about-ci
• https://docs-getdbt-com-git-nfiann-ci-and-git-dbt-labs.vercel.app/docs/deploy/ci-jobs
• https://docs-getdbt-com-git-nfiann-ci-and-git-dbt-labs.vercel.app/docs/deploy/continuous-integration

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
docs-getdbt-com	✅ Ready (Inspect)	Visit Preview	Jan 9, 2025 11:34am

[mirnawong1]

looks much better, thanks for linking the snippet in other pages @nataliefiann ! approved and one question that can be followed up with another pr - should the table include api functionality? eg how you can trigger a job via the cloud api: https://docs.getdbt.com/docs/deploy/ci-jobs#trigger-a-ci-job-with-the-api?

[joellabes]

Content looks great, suggested a tweaked title but can be workshopped further as needed!

[joellabes]

Suggested change

	- For providers without native integration, you can still use the git clone method to import your git URL or leverage the [dbt Cloud Administrative API](/docs/dbt-cloud-apis/admin-cloud-api) to trigger a CI job to run.
	- For providers without native integration, you can still use the git clone method to import your git URL and leverage the [dbt Cloud Administrative API](/docs/dbt-cloud-apis/admin-cloud-api) to trigger a CI job to run.

[joellabes]

Suggested change

	## Git providers who support CI
	## Availability of features by Git provider

Suggest a title like this instead, since we say that CI jobs are possible for any provider if you trigger it with the admin API.

[joellabes]

Suggested change

	title="Git providers who support CI"
	body="Learn which Git providers support CI"
	title="Availability of CI features by Git provider"
	body="Learn which Git providers have native support for Continuous Integration workflows"

Same comment as below - open to alternative phrasing on this though