-
Notifications
You must be signed in to change notification settings - Fork 9
Add contributors #249
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
base: main
Are you sure you want to change the base?
Add contributors #249
Conversation
❌ 1 Tests Failed:
View the top 1 failed test(s) by shortest run time
To view more test analytics, go to the Test Analytics Dashboard |
|
@mmcdermott do we want to use uv for version management? I have no experience with it so far. |
|
We should eventually for sure @rvandewater , but it will take a dedicated PR to get it added. |
|
I think the test failure is because we need to incorporate commit a233132 to update the MIMIC ETL version. |
|
@mmcdermott seems to be meds-tab related: https://github.com/Medical-Event-Data-Standard/MEDS-DEV/actions/runs/18461127482/job/52592654691?pr=250 |
| environment: | ||
|
|
||
| ```bash | ||
| uv sync |
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.
@rvandewater does this actually work for MEDS-DEV? If so, we should commit and merge straight away, if not we need to update.
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.
@mmcdermott, I haven't worked with UV before, but a quick try runs into errors for me. Is there a reason we would require people to work with a certain environment manager? Otherwise, I would just say install pre-commit and run tests in your favorite environment manager.
|
Basically the reason to use UV or poetry or anything is that the version
specifier you make for installation may be less precise than the version
specifiers for development. But given we don't have it set up for MEDS-DEV
yet, we should just tell them to use more standard tools for now.
…On Tue, Oct 14, 2025, 5:24 AM Robin van de Water ***@***.***> wrote:
***@***.**** commented on this pull request.
------------------------------
In CONTRIBUTORS.md
<#249 (comment)>
:
> +
+## Good Practice
+
+- Discuss large changes with the maintainers before significant work begins.
+- Keep commits focused and provide clear commit messages.
+- Include tests for new functionality and bug fixes.
+- Ensure documentation is updated for user-facing changes.
+
+## Installing the Project for Development
+
+This project uses [`uv`](https://docs.astral.sh/uv/) for environment management. To set up the project for
+development, simply clone the repository, then sync the uv environment, activate it, and install the pre-commit
+environment:
+
+```bash
+uv sync
@mmcdermott <https://github.com/mmcdermott>, I haven't worked with UV
before, but a quick try runs into errors for me. Is there a reason we would
require people to work with a certain environment manager? Otherwise, I
would just say install pre-commit and run tests in your favorite
environment manager.
—
Reply to this email directly, view it on GitHub
<#249 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADS5XZCWJHS3HNSJBZFB2L3XS6MDAVCNFSM6AAAAACICQX5LCVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZTGMZUGY4DMMBVGU>
.
You are receiving this because you were mentioned.Message ID:
***@***.***
com>
|
Taken directly from https://github.com/McDermottHealthAI/MHAL-template/blob/main/CONTRIBUTORS.md#installing-the-project-for-development