CI/CD processes for python libraries #14
Replies: 6 comments 1 reply
-
Trusted publishing@cortadocodes updated django-twined to use trusted publishing, featuring:
|
Beta Was this translation helpful? Give feedback.
-
CodeQL@cortadocodes updated django-twined (in this pr) to add CodeQL analysis. This isn't considered a 'check' on a PR, but rather gives a general status badge for the repository. It's in a separate |
Beta Was this translation helpful? Give feedback.
-
Semantic version checker@cortadocodes added the Compared to putting it in its own |
Beta Was this translation helpful? Give feedback.
-
Running pre-commit in CIWe should be runnign precommit in CI. Here's why and how: |
Beta Was this translation helpful? Give feedback.
-
Test PublishingFor the publish-test actions, we should be testing in parallel with any actual test matrix. First because it tests a different thing, Second because it gives us a clearer view of the complete picture. Discussion here: |
Beta Was this translation helpful? Give feedback.
-
Import sorting via
|
Beta Was this translation helpful? Give feedback.
-
This discussion is an ongoing thread about the latest developments in our CI/CD processes.
The aim is that when we take over maintenance of a library, or we come back to maintaining something we haven't touched for a while, we can skim down the notes here to catch up on what updates to our best practices have been made since the last time we touched that library, including pointers to where in our libraries you'd find and example of the latest best practice.
SORT BY NEWEST FIRST TO SEE MOST RECENT UPDATES!
Beta Was this translation helpful? Give feedback.
All reactions