Skip to content

feat: Clarify the semantics of src_key and dst_key - #218

Open
HalfSweet wants to merge 4 commits into
masterfrom
refactor_key
Open

feat: Clarify the semantics of src_key and dst_key#218
HalfSweet wants to merge 4 commits into
masterfrom
refactor_key

Conversation

@HalfSweet

Copy link
Copy Markdown
Collaborator

No description provided.

@HalfSweet HalfSweet linked an issue Jan 20, 2026 that may be closed by this pull request

@Yikun Yikun left a comment

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

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

Overall, LGTM, Please also add a e2e test and fullfill PR message

Comment thread hub-mirror/mirror.py
self.repo_path,
kill_after_timeout=self.timeout,
)
if self._uses_ssh_for_src():

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

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

Please add note here to show branch case

Comment thread README.md Outdated
with:
src: github/kunpengcompute
dst: gitee/kunpengcompute
src_key: ${{ secrets.GITHUB_PRIVATE_KEY }}

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

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

I suggested donot add this and add a new case for separate src_key and dst_key consider src_key is not a required parameter.

Keep simple will reduce new users onboard.

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.

feat: Clarify the semantics of src_key and dst_key

2 participants