Skip to content

Commit f1d980d

Browse files
committed
notes on feature branch
1 parent ec07a8a commit f1d980d

1 file changed

Lines changed: 16 additions & 5 deletions

File tree

README.md

Lines changed: 16 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -10,9 +10,10 @@
1010

1111
* `pytest` for tests: `make test`
1212
* `ruff` for linting/formatting: `make lint` (replaces both `black` and `isort`)
13+
* [pyproject-pipenv](https://github.com/fopina/pyproject-pipenv) to make sure dependencies in pyproject.toml and Pipfile are in sync
1314
* `.github` with actions ready to be used
14-
* [test](.github/workflows/test.yml) runs lint checks and unit tests
15-
* [publish-dev](.github/workflows/publish-dev.yml) publishes feature branches (`dev`/`dev-*`) to [testpypi](https://test.pypi.org)
15+
* [test](.github/workflows/test.yml) runs lint checks, unit tests and pyproject-pipenv
16+
* [publish-dev](.github/workflows/publish-dev.yml) publishes feature branches (`dev`/`dev-*`) to [testpypi](https://test.pypi.org) - more about this on [Notes](#feature-branch-publishing)
1617
* [publish-main](.github/workflows/publish-main.yml) publishes semver tags to [pypi](https://pypi.org)
1718

1819
## New project checklist
@@ -24,9 +25,19 @@
2425
* `PYPI_USERNAME` and `PYPI_TOKEN` to publish tags to pypi
2526
* `TESTPYPI_USERNAME` and `TESTPYPI_TOKEN` to publish dev branches to testpypi
2627
* [ ] Replace this README.md - template below
27-
---
28-
---
29-
---
28+
29+
## Notes
30+
31+
### Feature branch publishing
32+
33+
`publish-dev` workflow publishes `dev`/`dev-*` branches to [testpypi](https://test.pypi.org).
34+
35+
Other common approach to publish dev branches is to use pre-release channels: version the package with a `rc` or `beta` suffix (such as `1.0.0-beta1`) and pypi will consider pre-release. In order to install this, the user needs to do `pip install PACKAGE --pre` otherwise the latest stable is picked up.
36+
However this will "pollute" your pypi index and it still requires you to bump the version (`1.0.0-beta1` < `1.0.0`) or to install the branch using specific version.
37+
38+
Yet another approach is to simply use an entirely different package name for the dev releases. Tensorflow does that, for example, with [tf-nightly](https://pypi.org/project/tf-nightly/).
39+
40+
## ---
3041

3142
# fp-github-template-example
3243

0 commit comments

Comments
 (0)