test: Update git-clone StepAction to tekton v1beta1 by chmouel · Pull Request #2450 · tektoncd/pipelines-as-code

chmouel · 2026-02-05T10:13:59Z

Changed the apiVersion of the git-clone StepAction from tekton.dev/v1alpha1 to tekton.dev/v1beta1. This was done to align with the current stable API version for Tekton resources.

📝 Description of the Change

👨🏻‍ Linked Jira

🔗 Linked GitHub Issue

Fixes #

🚀 Type of Change

🧪 Testing Strategy

🤖 AI Assistance

I have not used any AI assistance for this PR.
I have used AI assistance for this PR.

If you have used AI assistance, please provide the following details:

Which LLM was used?

Extent of AI Assistance:

Documentation and research only
Unit tests or E2E tests only
Code generation (parts of the code)
Full code generation (most of the PR)
PR description and comments
Commit message(s)

Important

If the majority of the code in this PR was generated by an AI, please add a Co-authored-by trailer to your commit message.
For example:

Co-authored-by: Gemini gemini@google.com
Co-authored-by: ChatGPT noreply@chatgpt.com
Co-authored-by: Claude noreply@anthropic.com
Co-authored-by: Cursor noreply@cursor.com
Co-authored-by: Copilot Copilot@users.noreply.github.com

**💡You can use the script ./hack/add-llm-coauthor.sh to automatically add
these co-author trailers to your commits.

✅ Submitter Checklist

Changed the apiVersion of the git-clone StepAction from tekton.dev/v1alpha1 to tekton.dev/v1beta1. This was done to align with the current stable API version for Tekton resources.

qodo-code-review · 2026-02-05T10:14:05Z

❌ PR-Agent failed to apply 'global' repo settings

The configuration file needs to be a valid TOML, please fix it.

Error message:
cannot access local variable 'file_data' where it is not associated with a value

Configuration content:

[github_app]
pr_commands = [ "/review" ]

[pr_reviewer]
enable_review_labels_security = true
enable_chat_in_code_suggestions=false
enable_chat_in_code_suggestions = false
enable_summary=false
enable_help_text=false

[pr_description]
publish_description_as_comment = true

[pr_code_suggestions]
commitable_code_suggestions = true

[pr_test]
num_tests = 0

gemini-code-assist · 2026-02-05T10:14:10Z

Summary of Changes

Hello @chmouel, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request updates the git-clone Tekton StepAction to utilize the v1beta1 API version, ensuring compatibility and alignment with the latest stable Tekton API. The change primarily involves a version bump in the YAML definition and minor formatting adjustments to the environment variable declarations.

Highlights

API Version Update: The apiVersion for the git-clone StepAction has been updated from tekton.dev/v1alpha1 to tekton.dev/v1beta1 to align with the current stable API version for Tekton resources.
YAML Formatting: Minor YAML formatting adjustments were made to the env section within the spec of the StepAction, specifically regarding indentation of environment variables.

Changelog

.tekton/stepactions/git-clone.yaml
- Updated apiVersion from tekton.dev/v1alpha1 to tekton.dev/v1beta1.
- Adjusted YAML indentation for environment variables within the env section.

Activity

The pull request was created by chmouel with a clear description of the intent to update the Tekton API version.
No further review comments or activity have been recorded yet.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	`/gemini review`	Performs a code review for the current pull request in its current state.
Pull Request Summary	`/gemini summary`	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	`/gemini help`	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

pipelines-as-code · 2026-02-05T10:14:27Z

🔍 PR Lint Feedback

Note: This automated check helps ensure your PR follows our contribution guidelines.

⚠️ Items that need attention:

🎫 Jira reference

Add a Jira reference in the description using one of the following formats:

https://issues.redhat.com/browse/SRVKP-<number>

If no SRVKP ticket exists yet, link a GitHub issue instead (e.g., Fixes #123).
Minor housekeeping PRs without Jira coverage can skip this after confirming with reviewers.

🤖 AI attribution

The following commits lack an explicit AI attribution footer:

eb5bc25 fix: Update git-clone StepAction to tekton v1beta1

If no AI assistance was used for a commit, you can ignore this warning.
Otherwise add an Assisted-by: or Co-authored-by: footer referencing the AI used.

ℹ️ Next Steps

Review and address the items above
Push new commits to update this PR
This comment will be automatically updated when issues are resolved

🔧 Admin Tools (click to expand)

Automated Issue/Ticket Creation:

/issue-create - Generate a GitHub issue from this PR content using AI
/jira-create - Create a SRVKP Jira ticket from this PR content using AI

⚠️ Important: Always review and edit generated content before finalizing tickets/issues.
The AI-generated content should be used as a starting point and may need adjustments.

These commands are available to maintainers and will post the generated content as PR comments for review.

_{🤖 This feedback was generated automatically by the PR CI system}

Copilot

Pull request overview

This PR updates the git-clone StepAction API version from tekton.dev/v1alpha1 to tekton.dev/v1beta1, aligning it with the current stable API version for Tekton StepAction resources and making it consistent with other StepAction files in the repository.

Changes:

Updated apiVersion from tekton.dev/v1alpha1 to tekton.dev/v1beta1
Standardized YAML indentation for the env section

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot · 2026-02-05T10:16:40Z

.tekton/stepactions/git-clone.yaml

@@ -1,4 +1,4 @@
-apiVersion: tekton.dev/v1alpha1
+apiVersion: tekton.dev/v1beta1


The PR title begins with "test:" suggesting this is a test-related change, but this file is not a test file - it's a StepAction definition that is used by test pipelines. The PR title should more accurately reflect the nature of the change, such as "chore: Update git-clone StepAction to tekton v1beta1" or "feat: Migrate git-clone StepAction from v1alpha1 to v1beta1". According to the PR description template, the type of change should match the commit message prefix.

gemini-code-assist

Code Review

This pull request correctly updates the git-clone StepAction to use apiVersion: tekton.dev/v1beta1, aligning with the stable Tekton API. Additionally, it fixes an indentation issue in the env section, ensuring the YAML is valid. I've found one minor improvement opportunity regarding a quoted parameter value that should be addressed. Otherwise, the changes are straightforward and correct.

gemini-code-assist · 2026-02-05T10:17:16Z

.tekton/stepactions/git-clone.yaml

+    - name: HOME
+      value: "$(params.userHome)"


The value for the HOME environment variable is quoted. Tekton's parameter substitution will result in the HOME variable being set to a string that includes the quotes (e.g., "/tekton/home" instead of /tekton/home). This is likely not the intended behavior and could cause issues with tools that expect a clean path in the HOME variable. It should be unquoted to match the style of other parameter substitutions in this file.

- name: HOME value: $(params.userHome)

fix: Update git-clone StepAction to tekton v1beta1

eb5bc25

Changed the apiVersion of the git-clone StepAction from tekton.dev/v1alpha1 to tekton.dev/v1beta1. This was done to align with the current stable API version for Tekton resources.

Copilot AI review requested due to automatic review settings February 5, 2026 10:14

Copilot started reviewing on behalf of chmouel February 5, 2026 10:14 View session

pipelines-as-code bot added fix testing labels Feb 5, 2026

chmouel merged commit a076d20 into tektoncd:main Feb 5, 2026
6 checks passed

chmouel deleted the update-tekton-git-clone-api-version branch February 5, 2026 10:15

Copilot AI reviewed Feb 5, 2026

View reviewed changes

gemini-code-assist bot reviewed Feb 5, 2026

View reviewed changes

chmouel restored the update-tekton-git-clone-api-version branch February 19, 2026 13:18

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

test: Update git-clone StepAction to tekton v1beta1#2450

test: Update git-clone StepAction to tekton v1beta1#2450
chmouel merged 1 commit intotektoncd:mainfrom
chmouel:update-tekton-git-clone-api-version

chmouel commented Feb 5, 2026 •

edited

Loading

Uh oh!

qodo-code-review bot commented Feb 5, 2026

Uh oh!

gemini-code-assist bot commented Feb 5, 2026

Uh oh!

pipelines-as-code bot commented Feb 5, 2026

Uh oh!

Uh oh!

Copilot AI left a comment

Uh oh!

Copilot AI Feb 5, 2026

Uh oh!

gemini-code-assist bot left a comment

Uh oh!

gemini-code-assist bot Feb 5, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

		@@ -1,4 +1,4 @@
		apiVersion: tekton.dev/v1alpha1
		apiVersion: tekton.dev/v1beta1

Conversation

chmouel commented Feb 5, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

📝 Description of the Change

👨🏻‍ Linked Jira

🔗 Linked GitHub Issue

🚀 Type of Change

🧪 Testing Strategy

🤖 AI Assistance

✅ Submitter Checklist

Uh oh!

qodo-code-review bot commented Feb 5, 2026

Uh oh!

gemini-code-assist bot commented Feb 5, 2026

Summary of Changes

Highlights

Footnotes

Uh oh!

pipelines-as-code bot commented Feb 5, 2026

🔍 PR Lint Feedback

⚠️ Items that need attention:

🎫 Jira reference

🤖 AI attribution

ℹ️ Next Steps

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Copilot AI Feb 5, 2026

Choose a reason for hiding this comment

Uh oh!

gemini-code-assist bot left a comment

Choose a reason for hiding this comment

Code Review

Uh oh!

gemini-code-assist bot Feb 5, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

chmouel commented Feb 5, 2026 •

edited

Loading