Skip to content

Commit d620c18

Browse files
committed
Initial commit
0 parents  commit d620c18

File tree

1 file changed

+49
-0
lines changed

1 file changed

+49
-0
lines changed

README.md

Lines changed: 49 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,49 @@
1+
# libvcell
2+
3+
[![Release](https://img.shields.io/github/v/release/virtualcell/libvcell)](https://img.shields.io/github/v/release/virtualcell/libvcell)
4+
[![Build status](https://img.shields.io/github/actions/workflow/status/virtualcell/libvcell/main.yml?branch=main)](https://github.com/virtualcell/libvcell/actions/workflows/main.yml?query=branch%3Amain)
5+
[![codecov](https://codecov.io/gh/virtualcell/libvcell/branch/main/graph/badge.svg)](https://codecov.io/gh/virtualcell/libvcell)
6+
[![Commit activity](https://img.shields.io/github/commit-activity/m/virtualcell/libvcell)](https://img.shields.io/github/commit-activity/m/virtualcell/libvcell)
7+
[![License](https://img.shields.io/github/license/virtualcell/libvcell)](https://img.shields.io/github/license/virtualcell/libvcell)
8+
9+
libvcell is a subset of VCell algorithms intended to support the [pyvcell](https://pypi.org/project/pyvcell/) python package. libvcell is available as a native executable and a python package.
10+
11+
- **Github repository**: <https://github.com/virtualcell/libvcell/>
12+
- **Documentation** <https://virtualcell.github.io/libvcell/>
13+
14+
## Getting started with your project
15+
16+
First, create a repository on GitHub with the same name as this project, and then run the following commands:
17+
18+
```bash
19+
git init -b main
20+
git add .
21+
git commit -m "init commit"
22+
git remote add origin git@github.com:virtualcell/libvcell.git
23+
git push -u origin main
24+
```
25+
26+
Finally, install the environment and the pre-commit hooks with
27+
28+
```bash
29+
make install
30+
```
31+
32+
You are now ready to start development on your project!
33+
The CI/CD pipeline will be triggered when you open a pull request, merge to main, or when you create a new release.
34+
35+
To finalize the set-up for publishing to PyPI or Artifactory, see [here](https://fpgmaas.github.io/cookiecutter-poetry/features/publishing/#set-up-for-pypi).
36+
For activating the automatic documentation with MkDocs, see [here](https://fpgmaas.github.io/cookiecutter-poetry/features/mkdocs/#enabling-the-documentation-on-github).
37+
To enable the code coverage reports, see [here](https://fpgmaas.github.io/cookiecutter-poetry/features/codecov/).
38+
39+
## Releasing a new version
40+
41+
- Create an API Token on [PyPI](https://pypi.org/).
42+
- Add the API Token to your projects secrets with the name `PYPI_TOKEN` by visiting [this page](https://github.com/virtualcell/libvcell/settings/secrets/actions/new).
43+
- Create a [new release](https://github.com/virtualcell/libvcell/releases/new) on Github.
44+
- Create a new tag in the form `*.*.*`.
45+
- For more details, see [here](https://fpgmaas.github.io/cookiecutter-poetry/features/cicd/#how-to-trigger-a-release).
46+
47+
---
48+
49+
Repository initiated with [fpgmaas/cookiecutter-poetry](https://github.com/fpgmaas/cookiecutter-poetry).

0 commit comments

Comments
 (0)