ci: Only upload artifacts in the XRPLF/rippled repository

[bthomee]

High Level Overview of Change

This change will only attempt to upload artifacts for CI runs performed in the XRPLF/rippled repository.

Context of Change

When we want to try out something new in a separate repository based on the rippled repository, the CI pipelines will fail when they try to upload the artifacts. We should only attempt to upload artifacts in the rippled repository.

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Refactor (non-breaking change that only restructures code)
• Performance (increase or change in throughput and/or latency)
• Tests (you added tests for code that already exists, or your new feature included in this PR)
• Documentation update
• Chore (no impact to binary, e.g. .gitignore, formatting, dropping support for older tooling)
• Release

[Copilot]

Pull request overview

Updates CI workflow guards so artifact- and package-upload steps only run when the workflow is executing in the canonical XRPLF/rippled repository, avoiding failures in downstream clones/forks that lack the required credentials or infrastructure.

Changes:

• Switch multiple workflow if: conditions from github.repository_owner == 'XRPLF' to github.repository == 'XRPLF/rippled'.
• Restrict Conan remote login/upload and recipe-upload jobs to only execute in XRPLF/rippled.
• Restrict binary artifact upload and Codecov upload to only execute in XRPLF/rippled.

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
.github/workflows/upload-conan-deps.yml	Restricts Conan remote login/upload steps to the XRPLF/rippled repo.
.github/workflows/reusable-build-test-config.yml	Restricts Linux binary artifact upload and Codecov upload to the XRPLF/rippled repo.
.github/workflows/on-trigger.yml	Restricts the develop-branch recipe upload job to the XRPLF/rippled repo.
.github/workflows/on-tag.yml	Restricts tag-triggered recipe upload job to the XRPLF/rippled repo.
.github/workflows/on-pr.yml	Restricts PR-based recipe upload job to the XRPLF/rippled repo.

---

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

[Copilot]

In a pull_request workflow, github.ref is typically refs/pull/<n>/merge (not the target branch). This startsWith(github.ref, 'refs/heads/release') check will never be true for PRs targeting release branches, so upload-recipe will be skipped. Use the PR base branch context instead (e.g., github.base_ref / github.event.pull_request.base.ref) and keep merge_group behavior in mind if it should also upload for merge queue runs. Also, the preceding comment says “XRPLF repository” but the condition now targets XRPLF/rippled; updating the comment would keep the intent clear.

[bthomee]

This will be fixed in a separate PR.

[bthomee]

See #6524.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 79.8%. Comparing base (24a5cba) to head (0281278).
⚠️ Report is 1 commits behind head on develop.

Additional details and impacted files

@@            Coverage Diff            @@
##           develop   #6523     +/-   ##
=========================================
- Coverage     79.8%   79.8%   -0.0%     
=========================================
  Files          862     862             
  Lines        67881   67881             
  Branches      7555    7558      +3     
=========================================
- Hits         54199   54185     -14     
- Misses       13682   13696     +14     

see 5 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.