aboutsummaryrefslogtreecommitdiffstats
path: root/.github (follow)
Commit message (Collapse)AuthorAgeLines
* `REPO_TOKEN` env var obliteratedGravatar Xithrius2022-10-12-1/+0
|
* Switch To Coveralls ActionGravatar Hassan Abouelela2022-09-30-5/+7
| | | | | | | | | | | The coveralls package has consistently caused issues for us, so it made sense to switch to something that's a little more decoupled, especially when it has official support. Switching is simple, since coverage.py can natively generate the format used by the coveralls action, and everything else is plug and play. Signed-off-by: Hassan Abouelela <[email protected]>
* Add DependabotGravatar Hassan Abouelela2022-09-30-0/+6
| | | | Signed-off-by: Hassan Abouelela <[email protected]>
* Upgrade To 3.10Gravatar Hassan Abouelela2022-09-30-1/+1
| | | | | | | All dependencies and code are already ready for 3.10, all that's necessary is to update the number. Signed-off-by: Hassan Abouelela <[email protected]>
* Merge branch 'main' into fix-warningsGravatar Hassan Abouelela2022-09-30-56/+6
|\
| * Fix Poetry 1.2 SupportGravatar Hassan Abouelela2022-09-18-56/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Poetry 1.2 introduced a regression which broke pip `--user` installs. These types of install where the main way we did installations in docker and CI, which made it much more convenient to control their location, availability, and caching. Poetry's team does not recognize this as a supported use case, so major changes were required to get everything working again. Most of the changes were consolidated into chrislovering/python-poetry-base for docker, and hassanabouelela/setup-python for CI. Signed-off-by: Hassan Abouelela <[email protected]>
* | Enable Python Warnings In TestsGravatar Hassan Abouelela2022-09-04-0/+1
|/ | | | | | | | There are currently no warnings emitted during our tests, so this is a low-cost method of ensuring we can better notice problems such as deprecation warnings earlier. Signed-off-by: Hassan Abouelela <[email protected]>
* Run Migrations For TestsGravatar Hassan Abouelela2022-07-12-1/+0
| | | | | | | Call the migration handler in manage.py when running tests, before handing control back to django. Signed-off-by: Hassan Abouelela <[email protected]>
* Remove resource suggestion template from siteGravatar mina2022-03-27-21/+0
| | | We will keep the issue template currently present on meta: https://github.com/python-discord/meta/blob/main/.github/ISSUE_TEMPLATE/resource-request.yaml
* Remove API change referencesGravatar Johannes Christ2022-03-07-9/+0
|
* Remove myself from the codeownersGravatar Matteo Bertucci2021-12-10-9/+4
|
* Error Out On Missing Files In CIGravatar Hassan Abouelela2021-10-10-0/+1
| | | | Signed-off-by: Hassan Abouelela <[email protected]>
* Merges DockerfilesGravatar Hassan Abouelela2021-10-10-3/+4
| | | | | | | Merges the normal dockerfile with the static build one to reduce duplication. Signed-off-by: Hassan Abouelela <[email protected]>
* Fixes Caching On Docker BuildGravatar Hassan Abouelela2021-10-10-13/+19
| | | | | | | Reworks the docker build action to use buildx in all steps to make the caching work. Reduces the wait time on the fetch action. Signed-off-by: Hassan Abouelela <[email protected]>
* Adds Netlify BuildsGravatar Hassan Abouelela2021-10-10-0/+69
| | | | | Adds an action which builds and uploads the static site as an artifact, and a fetch script to be run on the netlify builders.
* fix: clarify descirption of changes sectionGravatar Vivaan Verma2021-10-07-1/+1
|
* chore: Replace examples with commentsGravatar Vivaan Verma2021-10-07-6/+5
|
* chore: Add comments to instruct usersGravatar Vivaan Verma2021-10-07-1/+5
|
* Add a pull request templateGravatar Vivaan Verma2021-10-07-0/+19
| | | This pull request template was mainly added so that the second bullet point in [this PR comment](https://github.com/python-discord/api/pull/17#issuecomment-933739292) can be addressed.
* 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
|