aboutsummaryrefslogtreecommitdiffstats
path: root/.github (follow)
Commit message (Collapse)AuthorAgeLines
...
* Switches To Pytest As Test RunnerGravatar Hassan Abouelela2021-06-07-4/+1
| | | | | | | | Switches the test runner from unittest to pytest, to allow the usage of plugins such as xdist. This commit also adds pytest-cov purely as a generator for .coverage files. Signed-off-by: Hassan Abouelela <[email protected]>
* Updates Dependency Manager Files In CODEOWNERSGravatar Hassan Abouelela2021-05-11-1/+2
| | | | | | | Updates Pipfile and pipenv lock file to poetry equivalents in CODEOWNERS. Signed-off-by: Hassan Abouelela <[email protected]>
* Updates Usages Of Pipenv To PoetryGravatar Hassan Abouelela2021-05-11-11/+8
| | | | | | | Updates the Dockerfile, pre-commit, CI, and documentation to reflect the new dependency manager. Dockerfile is also updated to 3.9. Signed-off-by: Hassan Abouelela <[email protected]>
* Migrate GHCR_TOKEN -> GITHUB_TOKEN in Docker build actionGravatar ks1292021-04-05-1/+1
| | | GITHUB_TOKEN has now enough permissions to be used for pushing to GHCR, so we don't need PAT anymore.
* Add myself to CODEOWNERS (#1489)Gravatar Joe Banks2021-03-28-9/+9
|
* Added myself to CODEOWNERSGravatar wookie1842021-03-20-0/+1
|
* master => mainGravatar Joe Banks2021-03-13-5/+5
|
* Delete repo specific FUNDING.yml file in favour of org one in ↵Gravatar Joe Banks2021-03-09-2/+0
| | | | python-discord/.github
* DevOps team reviews for bot deploymentsGravatar Joe Banks2021-03-09-0/+1
|
* Update CODEOWNERSGravatar Boris Muratov2021-02-20-1/+5
|
* Fix wrong way for getting Git SHAGravatar ks1292020-12-20-1/+1
|
* Use bot prefix instead pydis-bot for Sentry release workflowGravatar ks1292020-12-20-1/+1
|
* Inject Git SHA in container build workflowGravatar ks1292020-12-20-0/+2
|
* Create workflow for creating Sentry releaseGravatar ks1292020-12-19-0/+24
|
* Add codeowner entries for ks129Gravatar ks1292020-12-16-1/+3
|
* Make sure PR build artifact is always uploadedGravatar Sebastiaan Zeeff2020-12-11-1/+1
| | | | | | | | | | GitHub Actions has an implicit status condition, `success()`, that is added whenever an `if` condition lacks a status function check of its own. In this case, while the upload step did check for the outcome of the previous "always" step, it did not have an actual status check and, thus, only ran on success. Since we always want to upload the artifact, even if other steps failed, I've added the "always" status function now.
* Send a custom workflow status embed to DiscordGravatar Sebastiaan Zeeff2020-12-10-0/+100
| | | | | | | | | | | | | | | | This commit introduces the same custom status embed as is already being used for Sir Lancebot. The default embeds GitHub sends are disabled, as they were causing slight issues with rate limits from time to time. It works like this: - The Lint & Test workflow stores an artifact with PR information, if we are linting/testing a PR. - Whenever we reach the end of a workflow run sequence, a status embed is send with the conclusion status. Signed-off-by: Sebastiaan Zeeff <[email protected]>
* Update CODEOWNERS for @Den4200Gravatar Dennis Pham2020-12-06-8/+5
|
* Create review-policy.ymlGravatar Joe Banks2020-12-06-0/+3
|
* Add myself to CODEOWNERSGravatar Boris Muratov2020-11-28-2/+3
|
* Add myself to CODEOWNERS for CI filesGravatar Sebastiaan Zeeff2020-11-27-1/+1
|
* Add @Akarys42 to the codeownersGravatar Matteo Bertucci2020-11-27-7/+14
|
* Merge pull request #1294 - Help Channel RefactorGravatar Mark2020-11-26-1/+1
|\
| * Update help channels directory for code ownersGravatar MarkKoz2020-11-26-1/+1
| |
* | Update CODEOWNERSGravatar Joe Banks2020-11-26-2/+6
|/
* Add Mark as a code owner of CI and Docker filesGravatar Mark2020-11-24-0/+5
|
* Specify code ownership for MarkGravatar MarkKoz2020-11-24-0/+19
|
* Update CODEOWNERSGravatar Dennis Pham2020-11-24-2/+2
|
* Update CODEOWNERSGravatar Joe Banks2020-11-24-1/+2
|
* Update CODEOWNERSGravatar Joe Banks2020-11-24-1/+1
|
* Open deployment.yaml from kubernetes repositoryGravatar Sebastiaan Zeeff2020-11-23-1/+4
| | | | | | | | We will now use the deployment information located in the private python-discord/kubernetes repository. The workflow will use a GitHub Personal Access Token to access this private repository. Signed-off-by: Sebastiaan Zeeff <[email protected]>
* Narrow down repository events that trigger a buildGravatar Sebastiaan Zeeff2020-11-23-1/+1
| | | | | | | | I've narrowed down repository events that trigger a Build to the "push" event specifically. This means that we never build for a "pull request" trigger, even if the source branch is called "master". Signed-off-by: Sebastiaan Zeeff <[email protected]>
* Checkout code so we can deployGravatar Sebastiaan Zeeff2020-11-19-0/+9
|
* Fix the deploy stage of our build pipelineGravatar Sebastiaan Zeeff2020-11-19-171/+30
| | | | | | | | | | I've fixed the deploy stage of our build pipeline, as it got mixed in with the old workflow file due to a merge conflict. The deploy stage is currently split into a separate workflow; theoretically, this allows us to trigger a redeploy from GitHub, without having to build the container image again. Signed-off-by: Sebastiaan Zeeff <[email protected]>
* Merge branch 'master' into kubernetes-deployGravatar Leon Sandøy2020-11-19-0/+172
|\
| * Add comment explaining buildx to workflowGravatar Sebastiaan Zeeff2020-11-19-0/+6
| | | | | | | | | | | | It's better to document these steps. Signed-off-by: Sebastiaan Zeeff <[email protected]>
| * Make sure we lint the actual pull requestGravatar Sebastiaan Zeeff2020-11-18-55/+64
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Unfortunately, our old setup did not actually lint the PR, as it was running in the context of the target repository. To sidestep the issue of using `pull_request_target` altogether, I've now changed our run of flake8 to using it directly and having it output its errors in teh format of Workflow Commands. This means that our flake8 output will not be translated automatically in annotations for the run. In addition, I've split up the workflow into two separate files: one for linting & testing and one for building (& deploying). Signed-off-by: Sebastiaan Zeeff <[email protected]>
* | Add deploy steps to GitHub ActionsGravatar Joe Banks2020-11-15-0/+14
|/
* Remove DockerHub from GitHub ActionsGravatar Sebastiaan Zeeff2020-11-15-11/+3
| | | | | | We don't use DockerHub anymore; let's remove it! Signed-off-by: Sebastiaan Zeeff <[email protected]>
* Push container to both DockerHub and GHCRGravatar Sebastiaan Zeeff2020-11-14-2/+22
| | | | | | | | To make the transition easier, we push the Docker container to both DockerHub and the GitHub Container Registry. I've also added a secondary tag by short commit SHA. Signed-off-by: Sebastiaan Zeeff <[email protected]>
* Add documentation to GitHub Actions stepsGravatar Sebastiaan Zeeff2020-11-14-5/+25
| | | | Signed-off-by: Sebastiaan Zeeff <[email protected]>
* Remove codeql analysis as it had little effectGravatar Sebastiaan Zeeff2020-11-14-32/+0
| | | | | | | The codeql analysis action we had proved to add little value to our test suite and has been removed. Signed-off-by: Sebastiaan Zeeff <[email protected]>
* Set flake8 action checkName to correct value Gravatar Sebastiaan Zeeff2020-11-14-1/+1
| | | | | The `checkName` value of this action needs to have the same value as the name of the job. Co-authored-by: Joe Banks <[email protected]>
* Stop Checkout Actions from persisting credentialsGravatar Sebastiaan Zeeff2020-11-14-2/+7
| | | | | | | | | | | | By default, the Checkout Actions persists the credentials in the environment. As our Actions will also run for PRs made from a fork, we don't want to persist credentials in such a way. I've also: - Ported a comment on PIP_USER and pre-commit from the azure configs - Removed unnecessary id for the pre-commit caching step Signed-off-by: Sebastiaan Zeeff <[email protected]>
* Add CI dependency coveralls to our PipfileGravatar Sebastiaan Zeeff2020-11-14-3/+1
| | | | | | | | | | The dependency `coveralls` was installed directly in GitHub Actions, as it's not required for local dev environments. However, it's a small package and there's value in keeping all our dependency specifications in one place. That's why I've moved it to the [dev] section of our Pipfile. Signed-off-by: Sebastiaan Zeeff <[email protected]>
* Migrate CI Pipeline to GitHub ActionsGravatar Sebastiaan Zeeff2020-11-14-0/+122
| | | | | | | | | | | | | | | | | | | | | | | I've migrated our Azure CI Pipeline to GitHub Actions. While the general workflow is the same, there are a few changes: - `flake8` is no longer run by `pre-commit`, but rather by a separate action that adds annotations to the GH Action results page. - As we no longer have need for xml-formatted coverage files, the xmlrunner for unittest has been removed as a dependency. Instead, we now publish our coverage results to coveralls.io. - We use version 2 of docker's GitHub Action build-and-push flow, which is split over multiple steps instead of one. - I have changed the badges to GitHub Actions and coveralls.io badges. Note: Because we accept PRs from forks, we need to be a bit careful with our secrets. While we do use the `pull_request_target` event, we should not expose secrets in steps that run code from the repository. Signed-off-by: Sebastiaan Zeeff <[email protected]>
* Fix trailing whitespace in 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
|
generated by cgit v1.2.3 (git 2.39.1) at 2025-11-08 14:20:00 +0000