Skip to content

Fix successive cloning issue #68

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

Merged
merged 13 commits into from
Mar 27, 2024
Merged

Fix successive cloning issue #68

merged 13 commits into from
Mar 27, 2024

Conversation

stephane-caron
Copy link
Member

Closes #67

@stephane-caron stephane-caron force-pushed the fix/clone_after_clone branch from b9aa375 to 3f3518e Compare March 27, 2024 16:55
@coveralls
Copy link

Pull Request Test Coverage Report for Build 8455781797

Details

  • 32 of 33 (96.97%) changed or added relevant lines in 9 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage decreased (-0.07%) to 98.563%

Changes Missing Coverage Covered Lines Changed/Added Lines %
robot_descriptions/loaders/mujoco.py 2 3 66.67%
Totals Coverage Status
Change from base Build 8454883283: -0.07%
Covered Lines: 960
Relevant Lines: 974

💛 - Coveralls

@stephane-caron stephane-caron merged commit 6af0b3d into main Mar 27, 2024
11 checks passed
@stephane-caron stephane-caron deleted the fix/clone_after_clone branch March 27, 2024 17:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

Loading non-specific after specific commit fails
2 participants