Skip to content

fix: update URLs after move to @pipelines-as-code#2619

Merged
chmouel merged 1 commit intotektoncd:mainfrom
chmouel:update-github-org-urls
Mar 28, 2026
Merged

fix: update URLs after move to @pipelines-as-code#2619
chmouel merged 1 commit intotektoncd:mainfrom
chmouel:update-github-org-urls

Conversation

@chmouel
Copy link
Copy Markdown
Member

@chmouel chmouel commented Mar 27, 2026

Updated references to the project's GitHub organization URLs to reflect the migration from openshift-pipelines to pipelines-as-code.

📝 Description of the Change

🔗 Linked GitHub Issue

Fixes #

🧪 Testing Strategy

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

🤖 AI Assistance

AI assistance can be used for various tasks, such as code generation,
documentation, or testing.

Please indicate whether you have used AI assistance
for this PR and provide details if applicable.

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

Important

Slop will be simply rejected, if you are using AI assistance you need to make sure you
understand the code generated and that it meets the project's standards. you
need at least know how to run the code and deploy it (if needed). See
startpaac to make it easy
to deploy and test your code changes.

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: Claude noreply@anthropic.com

✅ 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

Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request updates various documentation and test data files to reflect the migration of repositories from the openshift-pipelines organization to the pipelines-as-code organization. A review comment identifies a missed URL update in the test data that should be corrected to ensure consistency across the codebase.

Updated references to the project's GitHub organization URLs to reflect
the migration from `openshift-pipelines` to `pipelines-as-code`.

Signed-off-by: Chmouel Boudjnah <chmouel@redhat.com>
@chmouel chmouel force-pushed the update-github-org-urls branch from 65806bc to be07cdd Compare March 27, 2026 17:15
@chmouel chmouel merged commit 95a5344 into tektoncd:main Mar 28, 2026
12 of 14 checks passed
chmouel added a commit to chmouel/pipelines-as-code that referenced this pull request Mar 28, 2026
Corrected the repository URL for the git-clone stepaction to point to
the tektoncd organization.

This was a bad merge after tektoncd#2619
theakshaypant pushed a commit that referenced this pull request Mar 30, 2026
Corrected the repository URL for the git-clone stepaction to point to
the tektoncd organization.

This was a bad merge after #2619
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants