Skip to content

Conversation

yhakbar
Copy link
Contributor

@yhakbar yhakbar commented Sep 26, 2025

This is the holding PR for all the changes to support Pipelines v4.

Copy link

vercel bot commented Sep 26, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
docs Ready Ready Preview Comment Sep 29, 2025 3:05pm

Copy link
Contributor

coderabbitai bot commented Sep 26, 2025

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

✨ Finishing touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch pipelines-v4

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

  • Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
  • Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.


Comment @coderabbitai help to get the list of available commands and usage tips.

yhakbar and others added 2 commits September 26, 2025 13:18
* docs: Nested AWS into `Authenticating to the Cloud`

* docs: Adding Azure docs

* docs: Adding custom auth

* Fix build issues.

* Add custom page to sidebar

* Update docs/2.0/docs/pipelines/concepts/cloud-auth/aws.mdx

Co-authored-by: Josh Padnick <josh@gruntwork.io>

* Update docs/2.0/docs/pipelines/concepts/cloud-auth/aws.mdx

Co-authored-by: Josh Padnick <josh@gruntwork.io>

* fix: Use active voice for custom auth

* fix: Add examples of secret managers

* fix: Explicitly say 'at the root of your repository'

* fix: Add callout for risk of custom auth

* fix: Shuffle order of tabs for configuration options

* fix: Adding a bit of cleanup

* fix: Adding preamble for best practices

---------

Co-authored-by: Josh Padnick <josh@gruntwork.io>
@yhakbar yhakbar changed the title chore: Start of Pipelines v4 docs: Pipelines v4 Sep 26, 2025
* Add GitLab drift detection docs

* Add infrachanges to dictionary
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants