| Commit message (Collapse) | Author | Age | Lines |
| |\ |
|
| | |\ |
|
| | | |\ |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | |\ |
|
| | | | | |\
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
python-discord/migrate-nominations-to-nominations-models
Migrate nominations to the new Nomination model
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Before the migration to Django, we stored meta data on a nomination,
such as the `reason` and `end_reason`, in the infraction table using
"note" infractions, using a special prefix for the `reason`.
We have since decided to move nominations out of the infraction
context by creating a special `Nomination` model. However, given the
complexity of the data migration, we did not yet migrate the old
nomination data to this new model. This commit migrates that data by performing a data migration.
The data migration works as follows:
- Query all nomination data in chronological order;
- Replay all nominations and add them to the `Nomination` model;
- Delete the now obsolete `Infraction` entry.
In addition, this commit also adds a useful string representation for
`Nomination` objects.
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
Makes various minor changes to commas and formulations.
|
| | | |/ / /
| | | | |
| | | | |
| | | | |
| | | | | |
The new text was written by Tizzysaurus in his website cleanup
project, and lifted from his google doc.
|
| | |/ / / |
|
| | |/ /
|/| | |
|
| |/ / |
|
| |\ \
| | |
| | | |
Add link to Contributing landing page to our website's navbar
|
| | |/
| |
| |
| |
| | |
This commit adds a link to the Contributing landing page to the
navbar on our website.
|
| |/
|
|
|
|
|
|
|
| |
Currently, all toc-links will have a wiki-toc prefix. This commit
removes this prefix, so that we can header link with just something
like #environment instead of #wiki-toc-environment.
This addresses #276.
https://github.com/python-discord/site/issues/267
|
| |\ |
|
| | |\ |
|
| | | | |
|
| | | | |
|
| | |/ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
https://github.com/python-discord/site/issues/260
This commit adds validation steps to the InfractionSerializer to make
sure that `"warning"` infractions can never be set with `hidden=True`
and note infractions can never be set with `hidden=False` usng the
API. This is the final step in decoupling "note" infractions and
"warning" infractions.
This commit implements the final part of and closes #260
|
| |/
|
|
|
|
|
|
|
|
|
|
|
| |
https://github.com/python-discord/site/issues/260
We have added a new "note" type to the Infraction model, meaning that
we can now decouple notes and warnings completely. However, notes
made prior to this change are still registered as "hidden warnings".
This commit adds a data migration that sets the type field of "hidden
warning" infractions to "note".
This commit implements the first part of #260
|
| |\ |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The most recent infraction a user has is usually the most relevant to
us. This PR aims to make our life easier by sorting the infractions by
their `inserted_at` date, with the most recent insertion date first.
Note: The `id` is not entirely in chronological order, because we did
not import historical infractions in chronological order. That's why
the `inserted_at` field is specified instead of the `id` field.
|
| | |
| |
| | |
Co-Authored-By: Mark <[email protected]>
|
| | |
| |
| |
| | |
Co-Authored-By: Mark <[email protected]>
Co-Authored-By: Sebastiaan Zeeff <[email protected]>
|
| | | |
|
| |/ |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
The bug was caused by a naive approach to caching and retrieving the data.
This commit rectifies this by making the following changes:
- We will now cache for 1 hour instead of 10 minutes
- If the data is stale but API is rate limited, return cache, not crash.
- If the cache doesn't exist and API is rate limited, return dummy data,
and try again in 10 minutes.
This will prevent all crashes, and should still have more or less the same user experience.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Adding django.pythondiscord.com and django.api.pythondiscord.com
to ALLOWED_HOSTS to allow us to run Djangoify and migrate
the infraction data.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
This adds the Monokai, Friendly, and Darcula themes to this
repo. It leaves Darcula as the active theme. This can very
easily be changed later on by altering wiki/base.html
Resolves #243.
|
| |
|
|
|
|
| |
This will allow us to edit durations using the PATCH method,
which the bot implements already but which was overlooked
when this viewset was written.
|