| Commit message (Collapse) | Author | Age | Lines |
| |
|
| |
|
| |
|
|\
| |
| | |
Swap Metricity verified_at for joined_at
|
| | |
|
|/ |
|
| |
|
|\
| |
| | |
Include DestroyModelMixin to infractions view for DELETE method
|
| |\
| |/
|/| |
|
|\ \
| | |
| | |
| | |
| | | |
python-discord/bugfix/lemon/snekbox-not-showing-on-front-page
Increase per_page to 100 for GitHub API call.
|
|/ /
| |
| |
| |
| |
| |
| | |
Snekbox was being banished to page 2 and we were not iterating pages, so
it was not appearing in the data we got from our call to /repos. This
commit changes the request to use `per_page=100`, which will work at
least until we have >100 repos in our organisation.
|
|\ \
| | |
| | |
| | |
| | | |
python-discord/hotfix/lemon/front-page-project-sanity
Hotfix: Add some sanity to frontpage projects.
|
| | |
| | |
| | |
| | |
| | | |
I don't think we need to check for TypeError here, so that saves us the
trouble of testing these lines to appease coverage.
|
| | |
| | |
| | |
| | | |
This should restore 100% coverage.
|
| | |
| | |
| | |
| | |
| | | |
Instead of building "fake repos", we're now just omitting them, so this
test needs to be updated.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This rewrite will ensure we always return whichever repositories we're
able to resolve, and none of the others. It also shortens the code,
shrinks all the try/excepts, and generally makes things a little more
readable.
|
| | |
| | |
| | |
| | |
| | |
| | | |
Instead of showing an empty Projects section, we'll just omit it if we
can't resolve any of our projects. Otherwise, we'll show the projects we
can resolve.
|
|/ /
| |
| |
| |
| |
| | |
If no API data is available, the front page shouldn't crash and burn.
This commit will ensure the front page will just render without the
projects it can't get API data for instead of crashing the whole thing.
|
| |
| |
| |
| | |
When I changed the name of SITE_SENTRY_DSN to
SITE_DSN, I accidentally left an old reference in place.
|
| |
| |
| |
| |
| | |
The name of the environment variable was shortened during our
refactor of the Sentry secrets. Changed `settings.py` to reflect
that change.
|
| | |
|
| |
| |
| | |
We need to make sure that we always upload our PR artifact, even if linting/testing fails. As GitHub Actions inserts an implicit "success" status check if you don't add any explicit status checks, this means that we have to include an "always" status check, even if this step has a condition relying on another "always" step.
|
| |
| |
| |
| |
| |
| | |
Similar to Sir Lancebot and bot, I've added enhanced GitHub Actions
status embeds to our workflow sequence. This means we get fewer embeds,
but with more information!
|
| | |
|
| | |
|
|\ \
| | |
| | | |
Set max-requests-jitter parameter to gunicorn
|
| | |
| | |
| | | |
Co-authored-by: Sebastiaan Zeeff <[email protected]>
|
| | | |
|
|/ / |
|
| | |
|
|/
|
| |
Added this mixin and documented this in doctoring.
|
|\
| |
| |
| |
| | |
python-discord/sebastiaan/backend/refactor-deployment
Restructure Build & Deploy sequence in CI
|
| |\
| |/
|/| |
|
|\ \
| | |
| | | |
Remove Adafruit from front-page sponsors listing
|
| | | |
|
|/ / |
|
| |\
| |/
|/| |
|
| | |
|
| | |
|
| |\
| |/
|/| |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
I've renamed the file to create a more consistent naming scheme.
|
|/
|
|
|
|
|
|
|
|
|
|
|
| |
I've restructured the build & deploy sequence in our GitHub Actions CI
workflow:
- There's now a separate workflow to deploy to our cluster
- The Build workflow has an additional `if` check to ensure we're only
starting the build & deploy sequences for pushes to master
- We now checkout the python-discord/kubernetes repo to fetch the
deployment.yaml file located in there
|
| |
|
| |
|
|
|
| |
The CI was failing on occasion because postgres did not have time enough to start properly before we started running our makemigrations check. I've moved the docker-compose step to earlier in the workflow to give it some time to warm up.
|