chore: sync PR template types with linter config by zakisk · Pull Request #2522 · tektoncd/pipelines-as-code

zakisk · 2026-03-02T11:42:09Z

Add missing conventional commit types (style, perf, test, build, ci, revert) to the PR template to match the linter regex in .tekton/linter.yaml. Remove non-standard 'enhance' type that would fail CI validation.

Assisted-by: Claude Opus 4.6 (via Claude Code)

📝 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

Add missing conventional commit types (style, perf, test, build, ci, revert) to the PR template to match the linter regex in .tekton/linter.yaml. Remove non-standard 'enhance' type that would fail CI validation. Signed-off-by: Zaki Shaikh <zashaikh@redhat.com> Assisted-by: Claude Opus 4.6 (via Claude Code)

gemini-code-assist · 2026-03-02T11:42:22Z

Summary of Changes

Hello, 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 .github/pull_request_template.md file to align the available commit types with the project's conventional commit linter configuration. This ensures that developers use approved commit prefixes, improving commit history consistency and preventing issues during continuous integration validation.

Highlights

Conventional Commit Types Synchronization: Synchronized the list of conventional commit types in the pull request template with the project's linter configuration, ensuring consistency and preventing CI validation failures.
Removal of 'Enhance' Type: Removed the non-standard 'enhance' commit type from the PR template, as it was not recognized by the linter and would cause CI validation to fail.

Changelog

.github/pull_request_template.md
- Added style:, perf:, test:, build:, ci:, and revert: commit types to the checklist.
- Removed the enhance: commit type from the checklist.

Activity

The pull request author utilized AI assistance (Claude Opus 4.6) for full code generation.
The submitter checklist indicates that commit messages are clear, the type of change matches, and local make test and make lint commands were run.

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-03-02T11:42:31Z

🔍 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.

ℹ️ 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}

gemini-code-assist

Code Review

This pull request updates the PR template to align with the linter's conventional commit types. The review suggests adding the fix: type, which appears to be missing but is a standard type and referenced elsewhere in the template.

.github/pull_request_template.md

chmouel · 2026-03-02T16:43:11Z

.github/pull_request_template.md

 - [ ] 💥 Breaking change (`feat!:`, `fix!:`)
 - [ ] 📚 Documentation update (`docs:`)
- [ ] ⚙️ Chore (`chore:`)
+- [ ] 🎨 Style (`style:`)


it's too many of them @zakisk i was thinking to actually remove all of it since we enforce in the Github PR to have that in the title

yeah, agree. #2525

pipelines-as-code bot added the testing label Mar 2, 2026

gemini-code-assist bot reviewed Mar 2, 2026

View reviewed changes

.github/pull_request_template.md Show resolved Hide resolved

theakshaypant approved these changes Mar 2, 2026

View reviewed changes

theakshaypant merged commit 8fa0777 into tektoncd:main Mar 2, 2026
2 checks passed

chmouel reviewed Mar 2, 2026

View reviewed changes

zakisk deleted the update-pr-template branch March 2, 2026 19:18

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

chore: sync PR template types with linter config#2522

chore: sync PR template types with linter config#2522
theakshaypant merged 1 commit intotektoncd:mainfrom
zakisk:update-pr-template

zakisk commented Mar 2, 2026

Uh oh!

gemini-code-assist bot commented Mar 2, 2026

Uh oh!

pipelines-as-code bot commented Mar 2, 2026

Uh oh!

gemini-code-assist bot left a comment

Uh oh!

Uh oh!

Uh oh!

chmouel Mar 2, 2026

Uh oh!

zakisk Mar 2, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Conversation

zakisk commented Mar 2, 2026

📝 Description of the Change

👨🏻‍ Linked Jira

🔗 Linked GitHub Issue

🚀 Type of Change

🧪 Testing Strategy

🤖 AI Assistance

✅ Submitter Checklist

Uh oh!

gemini-code-assist bot commented Mar 2, 2026

Summary of Changes

Highlights

Footnotes

Uh oh!

pipelines-as-code bot commented Mar 2, 2026

🔍 PR Lint Feedback

⚠️ Items that need attention:

🎫 Jira reference

ℹ️ Next Steps

Uh oh!

gemini-code-assist bot left a comment

Choose a reason for hiding this comment

Code Review

Uh oh!

Uh oh!

Uh oh!

chmouel Mar 2, 2026

Choose a reason for hiding this comment

Uh oh!

zakisk Mar 2, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants