| Commit message (Collapse) | Author | Age | Lines |
| ... | |
| | | |\ \ \ \
| | |/ / / /
| |/| | | | |
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This should be all we need to enable the releases feature in Sentry for
this project.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
This is the first step in implementing releases for Sentry.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
This will make it easier to use in multiple places.
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
This will make the SHA available in all templates.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
This is required for gitpython to work.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
We'll need this to fetch the hash.
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
creation of User Models.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
UserListSerializer
`to_internal_value()` function is not longer overriden in UserListSerializer, this is due to explicitly stating the `id` field in UserSerializer as mentioned in the documentation.
Override `create()` method in UserListSerializer and override `get_serializer()` method in `UserViewSet` to support bulk creation.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
object from database.
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
implemented a method to handle bulk updates on user model via a new endpoint: /bot/users/bulk_patch
|
| | | |_|/ /
| |/| | |
| | | | |
| | | | | |
Pagination is done via PageNumberPagination, i.e, each page contains a specific number of `user` objects.
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | | |
rough first draft
|
| | |_|_|/
|/| | |
| | | |
| | | | |
add timeline route
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Revert commit 330a27926a7f2a9bdae56a5928cd81e55ccb38ed to reverse
changes made to 6c08da2f3e48db9c9dd452f2e0505c4a61e46592. Migrations
were failing when those changes were deployed.
|
| |\ \ \ \
| |/ / /
|/| | | |
Off-topic channel names non random selecting
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | |\ \ \
| |/ / /
|/| | | |
|
| |\ \ \ \
| |_|/ /
|/| | | |
Allow direct fetching of reminders by id
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| |/ / / |
|
| | | |
| | |
| | |
| | |
| | | |
This had the wrong data for GUILD_INVITES - it had invites instead of
Guild IDs. This new migration solves this problem.
|
| |\ \ \
| | | |
| | | | |
FilterList model and endpoints
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Now that we have a migration that adds data, we can no longer have tests
that operate on the assumption that the database is going to be empty.
So, we're now clearing that table before these tests run.
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
This will populate the table with domain names, guild invites, filter
tokens and file formats.
|
| | | | |
| | | |
| | | | |
Co-authored-by: Sebastiaan Zeeff <[email protected]>
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This really should've been handled automatically by DRF, and in the
future, it will be. But for now, we need to have constraints both on the
serializer (to get status code 400), and on the model (to prevent direct
database constraint violations).
See https://github.com/encode/django-rest-framework/issues/7173
|
| | | | | |
|
| | |\ \ \
| |/ / /
|/| | | |
|
| |\ \ \ \
| | | | |
| | | | | |
Add mentions field to Reminders model
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Since the mentions field stores static IDs and not foreign keys, there
is no need to create the objects for the test.
|
| | | | | | |
|
| | |\ \ \ \
| |/ / / /
|/| | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|