Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

fixed tables paths #31

Merged
merged 1 commit into from
Jun 18, 2024
Merged

fixed tables paths #31

merged 1 commit into from
Jun 18, 2024

Conversation

gianipez
Copy link
Collaborator

No description provided.

@kutschke kutschke requested a review from brownd1978 June 17, 2024 18:44
@kutschke kutschke self-assigned this Jun 17, 2024
@kutschke kutschke self-requested a review June 17, 2024 18:49
Copy link
Contributor

@kutschke kutschke left a comment

Choose a reason for hiding this comment

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

I have looked at all 3 PRs, this one and the ones in Offline and Production. The group looks OK to me.

The proposal is to merge this PR then immediately rerun the CI testing Offline and Production together. Presuming all goes well, merge right away. We are exposed to inconsistent repos if we merge this and do not promptly merge the other two.

Giani reports that he has tested the 3 together interactively and that the CI jobs that failed in the previous run now pass.

@brownd1978 I added you as a reviewer. Let me know if you want to review or pass on it.

@kutschke kutschke merged commit 5cad63d into Mu2e:main Jun 18, 2024
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants