| Commit message (Collapse) | Author | Age | Lines | ||
|---|---|---|---|---|---|
| ... | |||||
| | | | * | | (Tag Cleanup): Removed Tags from Administration | 2020-08-27 | -2/+0 | ||
| | | | | | | |||||
| | | | * | | (Tag Cleanup): Removed Tags viewset. | 2020-08-27 | -106/+0 | ||
| | |_|/ / |/| | | | |||||
| | | | * | Move the SHA into constants.py. | 2020-08-22 | -23/+4 | ||
| | | | | | | | | | | | | | | | | | The util was redundant. Thanks @MarkKoz | ||||
| | | | * | Remove the SHA from the wiki base.html | 2020-08-22 | -1/+0 | ||
| | | | | | | | | | | | | | | | | | | | | | This extends the regular base.html, so this would cause wiki pages to have two SHA's. | ||||
| | | | * | omit resources.py from coverage reports. | 2020-08-22 | -0/+1 | ||
| | | | | | | | | | | | | | | | | | | | | | I'm not writing the tests for that, it has nothing to do with this branch. | ||||
| | | | * | Move git SHA fetcher into its own file. | 2020-08-22 | -12/+26 | ||
| | | | | | | | | | | | | | | | | | Fix tests. | ||||
| | | | * | Move git SHA fetcher into utils. | 2020-08-22 | -9/+14 | ||
| | | | | | |||||
| | | | * | We need .git in the docker container for the SHA. | 2020-08-22 | -1/+0 | ||
| | | | | | |||||
| | | | * | Merge branch 'master' into add_deployment_info | 2020-08-22 | -1/+59 | ||
| | | | |\ | |_|_|/ |/| | | | |||||
| * | | | | Merge pull request #374 from Numerlor/reminder-direct-retrieve | 2020-08-20 | -1/+59 | ||
| |\ \ \ \ | | | | | | | | | | | Allow direct fetching of reminders by id | ||||
| | * | | | | Update docstring for new fetching behaviour | 2020-08-20 | -0/+24 | ||
| | | | | | | |||||
| | * | | | | Allow direct fetching of reminders by id | 2020-08-20 | -1/+35 | ||
| | | | | | | |||||
| | | | | * | Oops, remove double git install from Dockerfile. | 2020-08-22 | -3/+0 | ||
| | | | | | | |||||
| | | | | * | Create a GitHub Action to make a Sentry release. | 2020-08-22 | -0/+23 | ||
| | | | | | | | | | | | | | | | | | | | | | | | | | | This should be all we need to enable the releases feature in Sentry for this project. | ||||
| | | | | * | Set the sentry_sdk.init release to git_sha. | 2020-08-22 | -1/+3 | ||
| | | | | | | | | | | | | | | | | | | | | | This is the first step in implementing releases for Sentry. | ||||
| | | | | * | Move git SHA initialization to __init__.py. | 2020-08-22 | -4/+7 | ||
| | | | | | | | | | | | | | | | | | | | | | This will make it easier to use in multiple places. | ||||
| | | | | * | Optimize the git install in Dockerfile. | 2020-08-22 | -3/+7 | ||
| | | | | | | |||||
| | | | | * | Add a comment with the git SHA to base templates. | 2020-08-22 | -0/+2 | ||
| | | | | | | |||||
| | | | | * | Add a context processor that outputs the git SHA. | 2020-08-22 | -1/+11 | ||
| | | | | | | | | | | | | | | | | | | | | | This will make the SHA available in all templates. | ||||
| | | | | * | Install git in the docker environment. | 2020-08-22 | -0/+5 | ||
| | | | | | | | | | | | | | | | | | | | | | This is required for gitpython to work. | ||||
| | | | | * | Add gitpython ~=3.1.7 as a dependency. | 2020-08-22 | -90/+117 | ||
| | |_|_|/ |/| | | | | | | | | | | | We'll need this to fetch the hash. | ||||
| * | | | | Update Code Jam 7 to most recent in navbar | 2020-08-13 | -1/+1 | ||
| | | | | | |||||
| * | | | | Update rule 6 for the removal of #show-your-projects | 2020-08-08 | -1/+2 | ||
| |/ / / | |||||
| * | | | Fix bad migration 0059 | 2020-08-03 | -0/+85 | ||
| | | | | | | | | | | | | | | | | This had the wrong data for GUILD_INVITES - it had invites instead of Guild IDs. This new migration solves this problem. | ||||
| * | | | Merge pull request #371 from python-discord/whitelist_system | 2020-08-03 | -90/+600 | ||
| |\ \ \ | | | | | | | | | FilterList model and endpoints | ||||
| | * | | | Delete FilterList objects for tests. | 2020-07-30 | -0/+10 | ||
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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. | ||||
| | * | | | Add a migration for all the existing data. | 2020-07-30 | -0/+153 | ||
| | | | | | | | | | | | | | | | | | | | | | This will populate the table with domain names, guild invites, filter tokens and file formats. | ||||
| | * | | | Provide callable, not return value. | 2020-07-30 | -1/+1 | ||
| | | | | | | | | | | | | | Co-authored-by: Sebastiaan Zeeff <[email protected]> | ||||
| | * | | | Add a constraint in the DB model as well. | 2020-07-29 | -0/+15 | ||
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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 | ||||
| | * | | | Fix multiple leafs for migration graph. | 2020-07-29 | -1/+1 | ||
| | | | | | |||||
| | * | | | Merge branch 'master' into whitelist_system | 2020-07-29 | -3/+80 | ||
| | |\ \ \ | |/ / / |/| | | | |||||
| * | | | | Merge pull request #370 from python-discord/role-reminders | 2020-07-20 | -3/+80 | ||
| |\ \ \ \ | | | | | | | | | | | Add mentions field to Reminders model | ||||
| | * | | | | Fix misleading documentation | 2020-07-19 | -1/+1 | ||
| | | | | | | |||||
| | * | | | | Use literal integers for mentions ID in test | 2020-07-19 | -14/+2 | ||
| | | | | | | | | | | | | | | | | | | | | | | | | | | Since the mentions field stores static IDs and not foreign keys, there is no need to create the objects for the test. | ||||
| | * | | | | Merge migrations | 2020-07-16 | -0/+14 | ||
| | | | | | | |||||
| | * | | | | Merge branch 'master' of github.com:python-discord/site into role-reminders | 2020-07-16 | -42/+158 | ||
| | |\ \ \ \ | |/ / / / |/| | | | | |||||
| | * | | | | Add mentions field to valid data test | 2020-07-16 | -1/+14 | ||
| | | | | | | |||||
| | * | | | | Document more undocumented stuff | 2020-07-16 | -2/+6 | ||
| | | | | | | |||||
| | * | | | | Document PATCH for reminders | 2020-07-16 | -0/+16 | ||
| | | | | | | |||||
| | * | | | | Document POSTing mentions in ReminderViewSet | 2020-07-16 | -0/+1 | ||
| | | | | | | |||||
| | * | | | | Add migration for the mentions field in the Reminder model | 2020-07-16 | -0/+20 | ||
| | | | | | | |||||
| | * | | | | Document mentions in ReminderViewSet | 2020-07-16 | -0/+5 | ||
| | | | | | | |||||
| | * | | | | Return mentions from ReminderSerializer | 2020-07-16 | -1/+3 | ||
| | | | | | | |||||
| | * | | | | Add mentions field to Reminder model | 2020-07-16 | -0/+14 | ||
| | | | | | | |||||
| | | * | | | Add a test for checking duplicates. | 2020-07-29 | -0/+5 | ||
| | | | | | | |||||
| | | * | | | Handle unique validator in DRF, not Django. | 2020-07-29 | -15/+15 | ||
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | I was handling this in a Django vanilla kind of way, which was causing the constraint to return a 500 instead of a 400. This changes the approach to use the DRF way, and makes it return 400. It doesn't actually change the way anything behaves, other than returning the right status code. | ||||
| | | * | | | Rename AllowDenyList to FilterList | 2020-07-27 | -48/+47 | ||
| | | | | | | |||||
| | | * | | | Minor changes to tests, use subTest. | 2020-07-19 | -9/+4 | ||
| | | | | | | |||||
| | | * | | | Document the get_types endpoint. | 2020-07-19 | -0/+14 | ||
| | | | | | | |||||
| | | * | | | Relock with a newer version of pipenv | 2020-07-19 | -10/+39 | ||
| | | | | | | |||||