pipe-cd / pipe-cd/pipecd

bug(lambda): Retain repository name when parsing unknown Git providers for artifact versions

Open
#6,666 2 comments 0 reactions 1 assignee View on GitHub

@zyzzmohit is already working on this.

Since Apr 15, 2026.

kind/bug
Dominant language
Go
Stars
1.4k
Forks
364
Avg merge
1d 4h
Merged PRs (30d)
84

Description

What happened:

In pkg/app/piped/platformprovider/lambda/function.go, the FindArtifactVersions function looks at the Git URL to generate a commit hyperlink. If it encounters a Git host it doesn't explicitly recognize (like AWS CodeCommit or a self-hosted Git server), it falls back to a default: case where it zeroes out both the gitURL and the repoPath (repoPath = ""). This results in ArtifactVersion.Name being completely empty.

What you expected to happen:

While it makes sense for the gitURL hyperlink to be empty if the provider's web-viewer format is unknown, the parsed repoPath should NOT be zeroed out. Discarding it causes a completely blank artifact name/repository to be displayed in the PipeCD UI.

How to reproduce it:

Define a lambda source manifest where the git URL points to an unrecognized host (e.g., git: https://git.mycompany.com/my/repo.git). When viewing the deployment on the control-plane UI, the source artifact name displays as blank.

Environment:

  • piped version: master
  • control-plane version: master
  • Others: N/A

I am intending to submit a PR to safely retain the repoPath name for this :)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.