-
Notifications
You must be signed in to change notification settings - Fork 99
Add a job to sync github repo with Codehub #1818
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
we only sync our code to their side. Do we need to provide any compilation step here? |
@yhmtsai , currently, I only sync. The compilation is done with easybuild, so that will be handled externally. In a fashion similar to spack. |
Does anyone else have access to the documentation? maybe @fritzgoebel ? |
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. |
No, I do not mean avoiding sync the entire repo. |
There was a problem hiding this 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
Co-authored-by: Yu-Hsiang M. Tsai <19565938+yhmtsai@users.noreply.github.com>
I have updated the description. |
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