Add CI workflow to build against eic-shell#34
Conversation
Co-authored-by: wdconinc <4656391+wdconinc@users.noreply.github.com>
There was a problem hiding this comment.
Pull request overview
This PR adds a GitHub Actions CI workflow to enable automated build testing for pull requests and pushes to main. The workflow uses the eic-shell environment via CVMFS, following the pattern established in the EICrecon repository. This addresses the repository's lack of automated CI testing.
Key changes:
- Added workflow that triggers on push to main, pull requests, and manual dispatch
- Configured build job using eic_xl:nightly environment with standard CMake build commands
- Implemented concurrency control to cancel redundant workflow runs
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
I'm not very familiar with CI. Lgtm, but how could I test? |
Look at https://github.com/eic/eic-smear/actions/runs/19900950398/job/57044424341?pr=34 :-) |
If you want, suggest a test command to run to make sure it actually does what it is supposed to do. Or implement CTest unit tests :-D :-D |
|
Test command(s) would be easy, but for historical reasons, test data lives in https://github.com/eic/eicsmeardetectors, which presumably isn't even installed anymore. |
Repository lacked GitHub Actions CI for testing PRs. Added a minimal build workflow using the eic-shell environment, following the pattern from EICrecon.
Changes
.github/workflows/linux-eic-shell.ymlwith:main, PRs, and manual dispatcheic_xl:nightly)Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.