| Commit message (Collapse) | Author | Age | Lines | 
| | 
| 
| 
|  | 
https://github.com/python-discord/site/issues/305
 | 
| | 
| 
|  | 
This will prevent a 500 server error on our homepage when GitHub's API is down, allowing us to use the cached data we have instead.
 | 
| |  | 
 | 
| |  | 
 | 
| |  | 
 | 
| |  | 
 | 
| |  | 
 | 
| |\  
| | 
| |  | 
Bump django from 2.2.11 to 2.2.13
 | 
| |/  
|   
|   
|   
|   
|   
|    | 
Bumps [django](https://github.com/django/django) from 2.2.11 to 2.2.13.
- [Release notes](https://github.com/django/django/releases)
- [Commits](https://github.com/django/django/compare/2.2.11...2.2.13)
Signed-off-by: dependabot[bot] <[email protected]>
 | 
| |\  
| | 
| | 
| | 
| |  | 
python-discord/joseph/change-roles-field-to-postgres-array
Change roles field on user model to Postgres array
 | 
| | | 
| | 
| |  | 
Co-authored-by: Sebastiaan Zeeff <[email protected]>
 | 
| | |\  
| |/  
|/|    | 
 | 
| | | 
| | 
| |  | 
Changed `Most Recent: Game Jam 2020` to `Upcoming: Code Jam 7`
 | 
| | |  | 
 | 
| | |  | 
 | 
| | |  | 
 | 
| | |  | 
 | 
| | |  | 
 | 
| | |  | 
 | 
| | |  | 
 | 
| | |  | 
 | 
| | |  | 
 | 
| | |  | 
 | 
| |/  
|   
|   
|    | 
postgres array with roles
 | 
| |\  
| | 
| |  | 
No longer accept or track `avatar_hash`
 | 
| |/  
|   
|   
|   
|   
|    | 
This should completely remove avatar_hash from the site - both in our
tests, in the model itself, and from the database (as a result of the
migration).
 | 
| |\  
| | 
| |  | 
Update Game Jam from upcoming to most recent
 | 
| |/   | 
 | 
| |\   | 
 | 
| | |  | 
 | 
| | |  | 
 | 
| | |\  
| |/  
|/|    | 
 | 
| |\ \  
| | | 
| | |  | 
Fix broken link to Game Jam 2020 banner
 | 
| |/ /  
| |   
| |   
| |    | 
The asset was recently moved to a new directory.
 | 
| | |  | 
 | 
| |/   | 
 | 
| | 
| 
|  | 
I've added the Game Jam banner to the home page and made it link the Game Jam info page.
 | 
| | 
| 
|  | 
To draw attention to upcoming events, I've changed the events section of the "more" dropdown menu. It now has an events header, followed by the upcoming event, and a link to the general events page.
 | 
| |\  
| | 
| |  | 
Update contributor doc
 | 
| |/   | 
 | 
| |\  
| | 
| |  | 
Add more pre-commit hooks
 | 
| | | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| |  | 
This also means flake8 will output to stdout in CI now. It didn't
before because it output to an XML format for publishing.
Pre-commit creates its own environment in which it installs hooks. To
speed up runs, the pipeline will cache this for use with future jobs.
The cache will update if .pre-commit-config.yaml changes.
The flake8 pre-commit hook invokes flake8 via `pipenv run flake8`. It's
normally useful to use pipenv here cause it ensures flake8 is invoked
within the context of the venv. However, in CI, there is no venv -
dependencies are installed directly to the system site-packages.
`pipenv run` does not work in such case because it tries to create a new
venv if one doesn't exist (it doesn't consider the system interpreter to
be a venv).
This workaround (okay, it's a hack) creates an executable shell script
which replaces the original pipenv binary. The shell script simply
ignores the first argument (i.e. ignores `run` in `pipenv run`) and
executes the rest of the arguments as a command. It essentially makes
`pipenv run flake8` equivalent to just having ran `flake8`. When
pre-commit executes pipenv, the aforementioned script is what will run.
 | 
| | | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| |  | 
Hooks added:
* check-merge-conflict - checks for files with merge conflict strings
* check-toml - attempts to load all toml files to verify syntax
* check-yaml - attempts to load all yaml files to verify syntax
* end-of-file-fixer - ensures files end in a newline and only a newline
* mixed-line-ending - replaces mixed line endings with LF
* trailing-whitespace - trims trailing whitespace
* python-check-blanket-noqa - enforces that noqa annotations always
  occur with specific codes
Changes made to comply with new hooks:
* Remove trailing whitespaces
* Remove some useless noqa annotations
* Specify errors for noqa annotations
* Add missing newlines at end of files
See: python-discord/organisation#138
 | 
| |/   | 
 | 
| |\  
| | 
| | 
| | 
| |  | 
python-discord/deleted-messages-visible-line-endings
Make newlines visible in deleted messages
 | 
| | |\  
| |/  
|/|    | 
 | 
| |\ \  
| | | 
| | |  | 
Install wiki from PyPI
 | 
| | |\ \  
| |/ /  
|/| |    | 
 | 
| |\ \ \  
| | | | 
| | | |  | 
Fix missing logs when using Docker Compose
 | 
| | |\ \ \  
| |/ / /  
|/| | |    | 
 |