Skip to content

Conversation

pratikvn
Copy link
Member

@pratikvn pratikvn commented Mar 31, 2025

This PR adds a github sync workflow to sync the github repo to codehub when the main/develop/release branches have been updated for easy CI/CD within the CASTIEL-2 project.

The objective is that eventually Ginkgo will be automatically deployed on the EU supercomputers and available to users through Easybuild and EESSI

@pratikvn pratikvn added reg:ci-cd This is related to the continuous integration system. 1:ST:ready-for-review This PR is ready for review 1:ST:skip-full-test 1:ST:no-changelog-entry Skip the wiki check for changelog update labels Mar 31, 2025
@pratikvn pratikvn requested a review from a team March 31, 2025 08:56
@pratikvn pratikvn self-assigned this Mar 31, 2025
@yhmtsai
Copy link
Member

yhmtsai commented Mar 31, 2025

we only sync our code to their side. Do we need to provide any compilation step here?

@yhmtsai yhmtsai requested a review from a team March 31, 2025 09:23
@pratikvn
Copy link
Member Author

@yhmtsai , currently, I only sync. The compilation is done with easybuild, so that will be handled externally. In a fashion similar to spack.

@yhmtsai
Copy link
Member

yhmtsai commented Mar 31, 2025

Does anyone else have access to the documentation? maybe @fritzgoebel ?
does the sync only syncs the branch which triggers the event or the entire repo? probably the entire repo because you set the fetch-depth 0

@pratikvn
Copy link
Member Author

I think syncing the whole repo should not be an issue. We might want to trigger specific branches and/tags, and I believe there should be no specific downside to syncing all the branches and tags.

@yhmtsai
Copy link
Member

yhmtsai commented Mar 31, 2025

No, I do not mean avoiding sync the entire repo.
more on checking which one is what you would like to do because the pr description sounds more on only push certain branch not entire one.

Copy link
Member

@yhmtsai yhmtsai left a comment

Choose a reason for hiding this comment

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

I do not know the usage of arguments from git-repo-sync from CASTIEL2
Others look good to me

@yhmtsai yhmtsai requested review from a team and fritzgoebel March 31, 2025 11:02
Co-authored-by: Yu-Hsiang M. Tsai <19565938+yhmtsai@users.noreply.github.com>
@pratikvn
Copy link
Member Author

I have updated the description.

@pratikvn pratikvn merged commit cea1be7 into develop Mar 31, 2025
10 of 11 checks passed
@pratikvn pratikvn deleted the feat/castiel2/git-sync branch March 31, 2025 13:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

1:ST:no-changelog-entry Skip the wiki check for changelog update 1:ST:ready-for-review This PR is ready for review 1:ST:skip-full-test reg:ci-cd This is related to the continuous integration system.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants