Skip to content

Commit 5a43c6c

Browse files
committed
Merge branch 'main' into update-repo-url
# Conflicts: # .github/workflows/release.yml # docs/installation.md
2 parents 5cf1f01 + aaa5544 commit 5a43c6c

File tree

9 files changed

+10
-10
lines changed

9 files changed

+10
-10
lines changed

.github/workflows/release.yml

+2-2
Original file line numberDiff line numberDiff line change
@@ -4,8 +4,8 @@ on: push
44

55
env:
66
# Change these for your project's URLs
7-
PYPI_URL: https://pypi.org/p/best-practices
8-
PYPI_TEST_URL: https://test.pypi.org/p/best-practices
7+
PYPI_URL: https://pypi.org/p/django-commons-best-practices
8+
PYPI_TEST_URL: https://test.pypi.org/p/django-commons-best-practices
99

1010
jobs:
1111

CODE_OF_CONDUCT.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,3 @@
1-
# Django Commons Playground Code of Conduct
1+
# Code of Conduct
22

33
The best-practices project utilizes the [Django Commons Code of Conduct](https://github.com/django-commons/membership/blob/main/CODE_OF_CONDUCT.md).

docs/README.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# Documentation
22

3-
The documentation for Django Commons Playground serves as an example for what
3+
The documentation for Django Commons Best Practices serves as an example for what
44
a repository should contain. The structure doesn't have to be exactly the same
55
as this, but it's a starting point. Any docs is better than no docs. Maintained
66
and organized docs are the best docs.

docs/getting_started.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ after [installing the project](installation.md), you can use the functionality
55
as such:
66

77
```python
8-
from django_commons_playground import playground
8+
from django_commons_best_practices import playground
99

1010
print(playground.seesaw())
1111
print(playground.seesaw())

docs/installation.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -1,16 +1,16 @@
11
# Installation
22

3-
This section explains how to install `best-practices` to use within
3+
This section explains how to install `django-commons-best-practices` to use within
44
your project. It assumes you have a working installation of Python 3.
55

66
1. Create venv/virtualenv (`python -m venv venv`)
77
2. Activate venv/virtualenv (`source venv/bin/activate`)
8-
3. Install `best-practices` (`pip install best-practices`)
8+
3. Install `django-commons-best-practices` (`pip install django-commons-best-practices`)
99

1010
All together now:
1111

1212
```shell
1313
python -m venv venv
1414
source venv/bin/activate
15-
pip install best-practices
15+
pip install django-commons-best-practices
1616
```

pyproject.toml

+1-1
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ requires = ["setuptools>=61.0"]
33
build-backend = "setuptools.build_meta"
44

55
[project]
6-
name = "django_commons_playground"
6+
name = "django-commons-best-practices"
77
version = "1.1.0"
88
authors = [
99
{ name="Tim Schilling", email="[email protected]" },

tests/test_playground.py

+1-1
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
from unittest import TestCase
22

3-
from src.django_commons_playground import playground
3+
from src.django_commons_best_practices import playground
44

55

66
class TestPlayground(TestCase):

0 commit comments

Comments
 (0)