aboutsummaryrefslogtreecommitdiffstats
path: root/.github (follow)
Commit message (Collapse)AuthorAgeLines
* Update in accordance with python-discord/kubernetes#95Gravatar Joe Banks2021-09-04-1/+1
|
* Add cache purge step to CI deploy stage (#533)Gravatar Joe Banks2021-06-16-0/+6
|
* Create issue template for resource suggestions.Gravatar swfarnsworth2021-06-06-0/+21
|
* update CODEOWNERS to track poetry filesGravatar Chris2021-05-17-1/+2
|
* Bump lint flow to 3.9 and use poetryGravatar Chris2021-05-17-11/+8
|
* Migrate GHCR_TOKEN -> GITHUB_TOKEN in Docker build actionGravatar ks1292021-04-05-2/+2
| | | GITHUB_TOKEN has now enough permissions to be used for pushing to GHCR, so we don't need PAT anymore. Also, use `repository_owner` instead of the secret of username.
* Update deploy.yamlGravatar Joe Banks2021-03-14-0/+1
|
* master => mainGravatar Joe Banks2021-03-13-5/+5
|
* Change pydis-site to site in workflowGravatar ks1292020-12-21-1/+1
|
* Fix Git SHA getting in workflowGravatar ks1292020-12-20-1/+1
|
* Set Git SHA during build workflowGravatar ks1292020-12-20-0/+2
|
* Add codeowner entires for ks129Gravatar ks1292020-12-16-1/+4
|
* Make sure to always upload PR artifact Gravatar Sebastiaan Zeeff2020-12-11-1/+1
| | | 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.
* Send an enhanced workflow status embed to discordGravatar Sebastiaan Zeeff2020-12-10-0/+100
| | | | | | 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!
* Update CODEOWNERS for @Den4200Gravatar Dennis Pham2020-12-06-7/+4
|
* Create review-policy.ymlGravatar Joe Banks2020-12-06-0/+3
|
* Merge branch 'master' into sebastiaan/backend/refactor-deploymentGravatar Dennis Pham2020-11-28-4/+11
|\
| * Add myself to CODEOWNERS for CI filesGravatar Sebastiaan Zeeff2020-11-27-1/+1
| |
| * Add @Akarys42 to the codeownersGravatar Matteo Bertucci2020-11-27-4/+11
| |
* | Merge branch 'master' into sebastiaan/backend/refactor-deploymentGravatar Sebastiaan Zeeff2020-11-27-1/+14
|\|
| * Update CODEOWNERSGravatar Joe Banks2020-11-26-2/+5
| |
| * Specify code owernship for MarkGravatar Mark2020-11-24-0/+9
| |
| * Update CODEOWNERSGravatar Dennis Pham2020-11-24-2/+2
| |
| * Update CODEOWNERSGravatar Joe Banks2020-11-24-1/+2
| |
| * Update CODEOWNERSGravatar Joe Banks2020-11-24-1/+1
| |
* | Rename kubernetes-deployment.yaml to deploy.yamlGravatar Sebastiaan Zeeff2020-11-27-0/+0
| | | | | | | | I've renamed the file to create a more consistent naming scheme.
* | Restructure Build & Deploy sequence in CIGravatar Sebastiaan Zeeff2020-11-24-18/+49
|/ | | | | | | | | | | | | 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
* Start database at the beginning of the workflowGravatar Sebastiaan Zeeff2020-11-19-3/+5
| | | 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.
* Insert missing "jobs" yaml tagGravatar Sebastiaan Zeeff2020-11-19-1/+1
|
* Ensure that flake8 runs on PR changesGravatar Sebastiaan Zeeff2020-11-19-67/+83
| | | | | | | | | | | | Unfortunately, the way we previously set up our workflow caused flake8 to run on code already committed to master, not the changes made in a PR, because it ran in the context of the target branch. This is obviously useless when it comes to protecting our codebase from linting errors. I've now set up flake8 in a different way, using Workflow Commands to create error annotions. I've also split up the workflow into two separate workflows.
* Bump version down to 3.8Gravatar Leon Sandøy2020-11-15-1/+1
|
* Update build flow to deploy to KubernetesGravatar Joe Banks2020-11-15-2/+17
|
* Make the value of the CI env var 'True' Gravatar Leon Sandøy2020-11-15-1/+1
| | | This makes it clearer that the env var switches on or off "CI-mode"
* Migrate to GH Actions & GH Container RegistryGravatar Sebastiaan Zeeff2020-11-15-32/+157
| | | | | | I've migrated site to GitHub Actions and GitHub Container Registry. This also means that coverage results will be pushed to coveralls.io. This commit also removes the pretty useless codeql analysis action.
* Create a GitHub Action to make a Sentry release.Gravatar Leon Sandøy2020-08-22-0/+23
| | | | | This should be all we need to enable the releases feature in Sentry for this project.
* Fix trailing whitespace in GitHub Action fileGravatar Joseph Banks2020-06-11-1/+1
|
* Create codeql-analysis.ymlGravatar Joseph Banks2020-06-11-0/+32
|
* Update CODEOWNERSGravatar Joseph2020-02-02-1/+1
|
* Create CODEOWNERSGravatar Joseph2020-02-02-0/+1
|
* Add FUNDING.ymlGravatar sco12019-07-09-0/+2
|
* Replace GitHub with GitLab across the projectGravatar Gareth Coles2018-06-07-42/+0
|
* Update CONTRIBUTING.mdGravatar Gareth Coles2018-04-09-1/+2
|
* Create CONTRIBUTING.mdGravatar Gareth Coles2018-04-09-0/+41
generated by cgit v1.2.3 (git 2.39.1) at 2025-10-18 13:09:21 +0000