Skip to content
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

Update README.md #103

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Update README.md #103

wants to merge 2 commits into from

Conversation

HelenCEBM
Copy link

Amendments to readme template

Amendments to readme template
README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved

# DISCLAIMER
This repository contains highly technical content for technical users. It is not a research publication. It has been made public to support the OpenSAFELY [open science and transparency principles] (https://www.opensafely.org/about/#contributing-to-best-practice-around-open-science) and to support the sharing of re-usable code for other subsequent users of the OpenSAFELY platform.
This repository must be interpreted in context: it may reflect the final codebase for a published project; or it may be an incomplete project; or have other shortcomings to be expected of a technical working document shared during development of the work.

Choose a reason for hiding this comment

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

Could we delete as appropriate here?

# DISCLAIMER
This repository contains highly technical content for technical users. It is not a research publication. It has been made public to support the OpenSAFELY [open science and transparency principles] (https://www.opensafely.org/about/#contributing-to-best-practice-around-open-science) and to support the sharing of re-usable code for other subsequent users of the OpenSAFELY platform.
This repository must be interpreted in context: it may reflect the final codebase for a published project; or it may be an incomplete project; or have other shortcomings to be expected of a technical working document shared during development of the work.
Therefore the contents of this repository MUST NOT be considered an accurate or valid representation of the study or its purpose.

Choose a reason for hiding this comment

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

I think they can be. Could this instead be

Therefore the contents of this repository may not be an accurate or valid representation of the study or its purpose.

@milanwiedemann milanwiedemann added the documentation Improvements or additions to documentation label Feb 7, 2024

Details of the purpose and any published outputs from this project can be found at the link above.
For your interest - to evaluate the code only, without any use of any actual patient data - you can execute the code for this project against randomly generated dummy patient data via [Gitpod](https://gitpod.io/) in a web browser by clicking on this badge: [![Gitpod ready-to-code]
Copy link
Contributor

Choose a reason for hiding this comment

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

This can be deleted, as Gitpod is no longer used/supported.

@iaindillingham
Copy link
Member

What would you like to do with this PR, @HelenCEBM?

  • fix the conflicts and merge?
  • close without merging
  • something else?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants