-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update workflows to run on GitHub #328
Conversation
This reverts commit 10e1052.
- Name all jobs and steps explicitly. - Ensure the names to come first in the YAML for readability. - Let the lint/typecheck jobs to use `PYTHON_LATEST` env-var.
* There seems no way to set "biweekly"...
.github/workflows/default.yml
Outdated
PYTHON_LATEST: "3.11" | ||
|
||
# For re-actors/checkout-python-sdist | ||
sdist-artifact: python-package-distributions | ||
|
||
jobs: | ||
lint-flake8: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How about separating the linting jobs into a dedicated reusable workflow?
.github/workflows/default.yml
Outdated
with: | ||
fetch-depth: 2 | ||
fetch-depth: 0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this bit really needed for linting?
.github/workflows/default.yml
Outdated
- run: python -Im pip install build | ||
name: Install core libraries for build and install | ||
- name: Build artifacts | ||
run: python -Im build |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since the linting jobs currently don't depend on this one, maybe it's a good idea to run twine check --strict
after this step. Alternatively, I'd put linting in a dedicated job.
@webknjaz Q. Should I add some |
We decided to migrate to |
For follow-ups, see #352. |
What do these changes do?
Run CI/CD jobs on GitHub instead of legacy Travis.
Are there changes in behavior for the user?
We can start releasing updates again, soon 😄
Related issue number
Branching off #327
Checklist
CHANGES
folder<issue_id>.<type>
(e.g.588.bugfix
)issue_id
change it to the pr id after creating the PR.feature
: Signifying a new feature..bugfix
: Signifying a bug fix..doc
: Signifying a documentation improvement..removal
: Signifying a deprecation or removal of public API..misc
: A ticket has been closed, but it is not of interest to users.Fix issue with non-ascii contents in doctest text files.