Skip to content

Conversation

@reshmifrog
Copy link
Contributor

  • All tests passed. If this feature is not already covered by the tests, I added new tests.
  • All static analysis checks passed.
  • Appropriate label is added to auto generate release notes.
  • I used gofmt for formatting the code before submitting the pull request.
  • PR description is clear and concise, and it includes the proposed solution/fix.

Added workflow to run cli e2e testcases.

@reshmifrog reshmifrog added the improvement Automatically generated release notes label Jan 20, 2026
@reshmifrog reshmifrog added the safe to test Approve running integration tests on a pull request label Jan 20, 2026
@github-actions
Copy link
Contributor

github-actions bot commented Feb 2, 2026

👍 Frogbot scanned this pull request and did not find any new security issues.


The checkout-jfrog-repos action was moving all files including .github
to the subdirectory, making composite actions inaccessible. Now .github
stays at root and is copied to the subdirectory for the Go module.
- Remove shell script file manipulation from checkout-jfrog-repos action
- Keep jfrog-cli-artifactory at root, checkout other repos to subdirectories
- Update go workspace to use "." for jfrog-cli-artifactory instead of subdirectory
- This is more reliable and avoids fragile file moving logic
@reshmifrog reshmifrog merged commit 8aef2f6 into jfrog:main Feb 2, 2026
10 of 11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

improvement Automatically generated release notes safe to test Approve running integration tests on a pull request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants