Skip to content

Commit 74ceb1b

Browse files
authored
Notes on updating this cookiecutter template
Closes #6
1 parent f60389b commit 74ceb1b

1 file changed

Lines changed: 7 additions & 0 deletions

File tree

README.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -92,3 +92,10 @@ Once you have created your account, navigate to https://pypi.org/manage/account/
9292
Now, any time you create a new "Release" on GitHub the Action will build your package and push it to PyPI.
9393

9494
The tag for your release needs to match the `VERSION` string at the top of your `pyproject.toml` file. You should bump this version any time you release a new version of your package.
95+
96+
## Notes on updating this cookiecutter template
97+
98+
Updating this cookiecutter template while keeping the [python-lib-template-repository](https://github.com/simonw/python-lib-template-repository) template repository working is a little bit complicated. Detailed notes in [issue #6](https://github.com/simonw/python-lib/issues/6), but the short version is:
99+
100+
1. Any changes to the `{{cookiecutter.hyphenated}}/.github/workflows/*.yml` files need to be manually pushed to the [python-lib-template-repository-demo](https://github.com/simonw/python-lib-template-repository-demo) repository, because GitHub Actions cannot update their own workflows.
101+
2. Generated final versions of those workflows then need to be copied to [python-lib-template-repository .github/workflows](https://github.com/simonw/python-lib-template-repository/tree/main/.github/workflows) for the same reason.

0 commit comments

Comments
 (0)