Skip to content

Commit 82f1f91

Browse files
authored
Adding a couple of README breadcrumbs for new users (#483)
* Adding README breadcrumbs in a couple of places. *Not* adding to ./src or ./tests at this point. * Adding a line about # Title in notebook README.
1 parent bc8bdee commit 82f1f91

File tree

3 files changed

+47
-0
lines changed
  • python-project-template

3 files changed

+47
-0
lines changed
Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,23 @@
1+
# The .github directory
2+
3+
This directory contains various configurations and .yml files that are used to
4+
define GitHub actions and behaviors.
5+
6+
## Workflows
7+
8+
The .yml files in ``./workflows`` are used to define the various continuous
9+
integration scripts that will be run on your behalf e.g. nightly as a smoke check,
10+
or when you create a new PR.
11+
12+
For more information about CI and workflows, look here: https://lincc-ppt.readthedocs.io/en/latest/practices/ci.html
13+
14+
## Configurations
15+
16+
Templates for various different issue types are defined in ``./ISSUE_TEMPLATE``
17+
and a pull request template is defined as ``pull_request_template.md``. Adding,
18+
removing, and modifying these templates to suit the needs of your project is encouraged.
19+
20+
For more information about these templates, look here: https://lincc-ppt.readthedocs.io/en/latest/practices/issue_pr_templating.html
21+
22+
23+
Or if you still have questions contact us: https://lincc-ppt.readthedocs.io/en/latest/source/contact.html
Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
# Benchmarks
2+
3+
This directory contains files that will be run via continuous testing either
4+
nightly or after committing code to a pull request.
5+
6+
The runtime and/or memory usage of the functions defined in these files will be
7+
tracked and reported to give you a sense of the overall performance of your code.
8+
9+
You are encouraged to add, update, or remove benchmark functions to suit the needs
10+
of your project.
11+
12+
For more information, see the documentation here: https://lincc-ppt.readthedocs.io/en/latest/practices/ci_benchmarking.html

python-project-template/{% if include_docs %}docs{% endif %}/notebooks/README.md

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -10,4 +10,16 @@ This means they should be able to be run with the resources in the repo, and in
1010

1111
This is great for notebooks that can run in a few minutes, on smaller datasets.
1212

13+
If you would like to include these notebooks in automatically generated documentation
14+
simply add the notebook name to the ``../notebooks.rst`` file, and include a markdown
15+
cell at the beginning of your notebook with ``# Title`` that will be used as the text
16+
in the table of contents in the documentation.
17+
18+
Be aware that you may also need to update the ``../requirements.txt`` file if
19+
your notebooks have dependencies that are not specified in ``../pyproject.toml``.
20+
1321
For notebooks that require large datasets, access to third party APIs, large CPU or GPU requirements, put them in `./pre_executed` instead.
22+
23+
For more information look here: https://lincc-ppt.readthedocs.io/en/latest/practices/sphinx.html#python-notebooks
24+
25+
Or if you still have questions contact us: https://lincc-ppt.readthedocs.io/en/latest/source/contact.html

0 commit comments

Comments
 (0)