chore: remove all commit prefix checks in pr template by zakisk · Pull Request #2525 · tektoncd/pipelines-as-code

zakisk · 2026-03-02T19:20:57Z

removed all commit prefix checks in PR template to not make noise in PR.

📝 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

removed all commit prefix checks in PR template to not make noise in PR. Signed-off-by: Zaki Shaikh <zashaikh@redhat.com>

gemini-code-assist · 2026-03-02T19:21:08Z

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 simplifies the .github/pull_request_template.md by removing the extensive 'Type of Change' section. This change is intended to streamline the pull request creation process by eliminating redundant checks and reducing visual clutter, allowing authors to focus on the core description of their changes without being prompted for commit prefix types within the PR body itself.

Highlights

PR Template Simplification: Removed the 'Type of Change' section from the pull request template, which previously listed various commit prefix checks (e.g., fix:, feat:, chore:).
Reduced Noise: The removal aims to reduce unnecessary noise and boilerplate in pull request descriptions, streamlining the PR creation process.

Changelog

.github/pull_request_template.md
- Removed the 'Type of Change' section, which included a list of conventional commit prefixes.

Activity

The pull request was opened by zakisk.
The author indicated that the change is a chore: type and marked 'Not Applicable' for testing strategy.
The author confirmed no AI assistance was used for the code, but Claude was used for the PR description and comments.

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-02T19:21:20Z

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

d7bb454 chore: remove all commit prefix checks in pr template

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}

gemini-code-assist

Code Review

This pull request removes the 'Type of Change' checklist from the PR template. While the specific comment addresses the obsolescence of a related item in the 'Submitter Checklist', it also emphasizes the importance of retaining guidance for conventional commit types like fix: in the template, as per repository rules. The suggestion is to modify the checklist item rather than simply deleting it, to ensure fix: remains explicitly included.

_{Note: Security Review has been skipped due to the limited scope of the PR.}

I am having trouble creating individual review comments. Click here to see my feedback.

.github/pull_request_template.md (12-28)

The 'Type of Change' section is being removed. However, the pull request template should still include guidance for conventional commit types like fix:, as it is a standard type. The current checklist item - [ ] ✨ I have ensured my commit message prefix (e.g., fix:, feat:) matches the "Type of Change" I selected above. refers to the removed section. Instead of removing this line entirely, consider modifying it to refer to a new section that explains conventional commit types, or rephrase it to stand alone, ensuring fix: is still explicitly mentioned as a standard type for commit messages.

References

The pull request template should include the fix: conventional commit type as it is a standard type.

chore: remove all commit prefix checks in pr template

d7bb454

removed all commit prefix checks in PR template to not make noise in PR. Signed-off-by: Zaki Shaikh <zashaikh@redhat.com>

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

zakisk mentioned this pull request Mar 2, 2026

chore: sync PR template types with linter config #2522

Merged

41 tasks

gemini-code-assist bot reviewed Mar 2, 2026

View reviewed changes

chmouel approved these changes Mar 2, 2026

View reviewed changes

zakisk merged commit f055cdf into tektoncd:main Mar 2, 2026
2 checks passed

zakisk deleted the remove-commit-prefix-checks branch March 2, 2026 19:35

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

chore: remove all commit prefix checks in pr template#2525

chore: remove all commit prefix checks in pr template#2525
zakisk merged 1 commit intotektoncd:mainfrom
zakisk:remove-commit-prefix-checks

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!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 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

🤖 AI attribution

ℹ️ Next Steps

Uh oh!

gemini-code-assist bot left a comment

Choose a reason for hiding this comment

Code Review

.github/pull_request_template.md (12-28)

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants