Skip to content

Move to tektoncd#2569

Merged
chmouel merged 3 commits intotektoncd:mainfrom
chmouel:move-to-tektoncd
Mar 12, 2026
Merged

Move to tektoncd#2569
chmouel merged 3 commits intotektoncd:mainfrom
chmouel:move-to-tektoncd

Conversation

@chmouel
Copy link
Copy Markdown
Member

@chmouel chmouel commented Mar 12, 2026 •
edited
Loading

📝 Description of the Change

Multiple commits to move to tektoncd, with one little go change comment to make it easy to test it.

👨🏻‍ Linked Jira

🔗 Linked GitHub Issue

Fixes #

🧪 Testing Strategy

  • Unit tests
  • Integration tests
  • End-to-end tests
  • Manual testing
  • Not Applicable

🤖 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?

  • GitHub Copilot
  • ChatGPT (OpenAI)
  • Claude (Anthropic)
  • Cursor
  • Gemini (Google)
  • Other: ____________

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

  • 📝 My commit messages are clear, informative, and follow the project's How to write a git commit message guide. The Gitlint linter ensures in CI it's properly validated
  • ✨ I have ensured my commit message prefix (e.g., fix:, feat:) matches the "Type of Change" I selected above.
  • ♽ I have run make test and make lint locally to check for and fix any
    issues. For an efficient workflow, I have considered installing
    pre-commit and running pre-commit install to
    automate these checks.
  • 📖 I have added or updated documentation for any user-facing changes.
  • 🧪 I have added sufficient unit tests for my code changes.
  • 🎁 I have added end-to-end tests where feasible. See README for more details.
  • 🔎 I have addressed any CI test flakiness or provided a clear reason to bypass it.
  • If adding a provider feature, I have filled in the following and updated the provider documentation:
    • GitHub App
    • GitHub Webhook
    • Gitea/Forgejo
    • GitLab
    • Bitbucket Cloud
    • Bitbucket Data Center

chmouel added 2 commits March 12, 2026 15:07
@chmouel
chore: migrate to tektoncd org
5899430 
Updated the default image repositories from openshift-pipelines to
tektoncd in the release generation script and the second controller
development tool to reflect the official project location.

Signed-off-by: Chmouel Boudjnah <chmouel@redhat.com>
@chmouel
test: add documentation to TestGiteaCancelRun
346a0fd 
Added a comment to the TestGiteaCancelRun function to clarify the
intended behavior of canceling pipeline runs via Gitea comments.
@pipelines-as-code
Copy link
Copy Markdown

pipelines-as-code bot commented Mar 12, 2026 •
edited
Loading

🔍 PR Lint Feedback

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

⚠️ Items that need attention:

📝 PR title format

Current title: Move to tektoncd

Expected format <type>(<scope>): <subject> with <type> one of [build, chore, ci, docs, deps, enhance, feat, dnm, fix, perf, refactor, release, revert, style, test].

Expected pattern: <type>(<scope>): <subject>
Allowed types: build, chore, ci, docs, deps, enhance, feat, dnm, fix, perf, refactor, release, revert, style, test

Examples:

  • fix(controller): ensure reconciler handles nil spec
  • docs: update contributing guide with lint instructions

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

  • 5899430 chore: migrate to tektoncd org
  • 346a0fd test: add documentation to TestGiteaCancelRun
  • 498fe62 chore: remove unused PipelineRuns in pac

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

@pipelines-as-code pipelines-as-code bot added documentation Improvements or additions to documentation refactoring tektoncd-migration Tasks related to tektoncd org migration labels Mar 12, 2026
@chmouel
chore: remove unused PipelineRuns in pac
498fe62 
Deleted the issue-create and jira PipelineRun definitions as they are no
longer required.
theakshaypant
theakshaypant reviewed Mar 12, 2026
View reviewed changes
Copy link
Copy Markdown
Member

@theakshaypant theakshaypant left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we also link the tekton guidelines like such

@chmouel
Copy link
Copy Markdown
Member Author

chmouel commented Mar 12, 2026

/retest

@chmouel
Copy link
Copy Markdown
Member Author

chmouel commented Mar 12, 2026

@theakshaypant i don't think so right now... as there is a bunch of prow specific stuff there...

@chmouel
Copy link
Copy Markdown
Member Author

chmouel commented Mar 12, 2026

will merge it to test release yaml gen

@chmouel chmouel merged commit a21ae43 into tektoncd:main Mar 12, 2026
16 checks passed
@chmouel
Copy link
Copy Markdown
Member Author

chmouel commented Mar 12, 2026 •
edited
Loading

ah damn the commit which has the go changes wsan't the last one so it didnt match and didn't stt the prun 🤦🏻

@chmouel chmouel deleted the move-to-tektoncd branch March 12, 2026 16:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@theakshaypant theakshaypant theakshaypant left review comments

Assignees

No one assigned

Labels

documentation Improvements or additions to documentation refactoring tektoncd-migration Tasks related to tektoncd org migration

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@chmouel @theakshaypant