https://github.com/birmingham-and-solihull-ics/git_exercise
Training repository
https://github.com/birmingham-and-solihull-ics/git_exercise
git github
Last synced: 2 months ago
JSON representation
Training repository
- Host: GitHub
- URL: https://github.com/birmingham-and-solihull-ics/git_exercise
- Owner: Birmingham-and-Solihull-ICS
- License: other
- Created: 2024-01-23T08:43:19.000Z (over 2 years ago)
- Default Branch: main
- Last Pushed: 2024-01-24T16:52:05.000Z (over 2 years ago)
- Last Synced: 2024-01-24T17:58:11.627Z (over 2 years ago)
- Topics: git, github
- Language: R
- Size: 7.81 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# BSOL sample project folder
This git repository contains a shell that should be used as the default structure for new projects
in the analytical team. It won't fit all circumstances perfectly, and you can make changes and issue a
pull request for new features / changes.
The aim of this template is two-fold: firstly to give a common structure for analytical projects to aid
reproducibility, secondly to allow for additional security settings as default to prevent accidental upload of files that should not be committed to Git and GitHub.
__Please update/replace this README file with one relevant to your project__
## To use this template, please use the following practises:
* Put any data files in the `data` folder. This folder is explicitly named in the .gitignore file. A further layer of security is that all xls, xlsx, csv and pdf files are also explicit ignored in the whole folder as well. ___If you need to commit one of these files, you must use the `-f` (force) command in `commit`, but you must be sure there is no identifiable data.__
* Save any documentation in the `docs` file. This does not mean you should avoid commenting your code, but if you have an operating procedure or supporting documents, add them to this folder.
* Please save all output: data, formatted tables, graphs etc. in the output folder. This is also implicitly ignored by git, but you can use the `-f` (force) command in `commit` to add any you wish to publish to github.
### Please also consider the following:
* Linting your code. This is a formatting process that follows a rule set. We broadly encourage the tidyverse standard, and recommend the `lintr` package.
* Comment your code to make sure others can follow.
* Consider your naming conventions: we recommend `snake case` where spaces are replaced by underscores and no capitals are use. E.g. `outpatient_referral_data`
This repository is dual licensed under the [Open Government v3]([https://www.nationalarchives.gov.uk/doc/open-government-licence/version/3/) & MIT. All code can outputs are subject to Crown Copyright.