diff options
| author | Markus Holtermann <info@markusholtermann.eu> | 2021-02-25 10:52:48 +0100 |
|---|---|---|
| committer | Mariusz Felisiak <felisiak.mariusz@gmail.com> | 2021-03-09 08:48:32 +0100 |
| commit | d9a266d657f66b8c4fa068408002a4e3709ee669 (patch) | |
| tree | b10eff95f3bef9840753d72609c4658001de9b22 /docs/internals/contributing/triaging-tickets.txt | |
| parent | a124365de80bd633e24f692e7ecaa5c84c12182d (diff) | |
Updated Git branch "master" to "main".
This change follows a long discussion on django-develops:
https://groups.google.com/g/django-developers/c/tctDuKUGosc/
Diffstat (limited to 'docs/internals/contributing/triaging-tickets.txt')
| -rw-r--r-- | docs/internals/contributing/triaging-tickets.txt | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/internals/contributing/triaging-tickets.txt b/docs/internals/contributing/triaging-tickets.txt index 950c03e4f4..8341ee0e3c 100644 --- a/docs/internals/contributing/triaging-tickets.txt +++ b/docs/internals/contributing/triaging-tickets.txt @@ -420,9 +420,9 @@ inadvertent side-effect. Here's how you can determine this. Begin by writing a regression test for Django's test suite for the issue. For example, we'll pretend we're debugging a regression in migrations. After you've -written the test and confirmed that it fails on the latest master, put it in a -separate file that you can run standalone. For our example, we'll pretend we -created ``tests/migrations/test_regression.py``, which can be run with:: +written the test and confirmed that it fails on the latest main branch, put it +in a separate file that you can run standalone. For our example, we'll pretend +we created ``tests/migrations/test_regression.py``, which can be run with:: $ ./runtests.py migrations.test_regression |
