-
Notifications
You must be signed in to change notification settings - Fork 10
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
GitHub actions #156
GitHub actions #156
Conversation
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.
This looks great. The GitHub Actions are a breath of fresh air. I tested desiInstall for a tag and a branch and both worked. Minor items for consideration but not blocking factors for merging:
- Consider shortening the names of the tests in
.github/workflows/python-package.yml
. When viewing the summary of tests in the github PR interface, the right side is getting cutoff (e.g. "CI / Check code style; allow failures. (ubuntu-latest, 3.8) (pull_request) Suc") even when I have the browser window maximally wide on my laptop, and the interface doesn't provide a horizontal slider. I presume that if the test failed it would be flagged obviously, but short names would help, e.g. something like "test", "coverage", "docs", "style". - very minor: could "desiInstall (package) main" be a shortcut for "desiInstall install branches/main" similar to "desiInstall (package) trunk"?
@sbailey, good suggestions. I'll get those in before merging. |
@sbailey, do you have other significant changes to desiutil planned for release 20.12? If not, I can tag desiutil after this merge. |
No other planned changes for desiutil for 20.12; please tag after merging. Thanks. |
This PR
master
is that all branches must be explicitly labeled as such. For exampledesiInstall desiutil branches/main
. Exception:desiInstall foo trunk
is an abbreviation fordesiInstall foo branches/trunk
.