Skip to content

Commit 960d14e

Browse files
authored
python-lib-template-demo
I deleted https://github.com/simonw/python-lib-template-repository-demo because it was an unmaintained dupe of https://github.com/simonw/python-lib-template-demo
1 parent 8f2475b commit 960d14e

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -97,5 +97,5 @@ The tag for your release needs to match the `VERSION` string at the top of your
9797

9898
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:
9999

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.
100+
1. Any changes to the `{{cookiecutter.hyphenated}}/.github/workflows/*.yml` files need to be manually pushed to the [python-lib-template-demo](https://github.com/simonw/python-lib-template-demo) repository, because GitHub Actions cannot update their own workflows.
101101
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)