-
-
Notifications
You must be signed in to change notification settings - Fork 0
feat: migrate from standalone actions #2
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
Conversation
Welcome to Codecov 🎉Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests. Thanks for integrating Codecov - We've got you covered ☂️ |
7fe4d2b
to
2ba5c21
Compare
b2b8957
to
e2edf77
Compare
9652760
to
0614c20
Compare
4f97130
to
13b825f
Compare
|
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.
Pull Request Overview
This PR migrates several standalone GitHub actions into a unified, reusable monorepo‐style structure. Key changes include the addition of new action implementations (for Python setup, release setup, Homebrew release, release creation, release changelog, and Facebook posting) and corresponding tests and CI configuration updates.
Reviewed Changes
Copilot reviewed 54 out of 60 changed files in this pull request and generated 2 comments.
File | Description |
---|---|
tests/... | New test modules added for each action (setup_python, release_setup, release_homebrew, release_create, release_changelog, facebook_post) to validate expected behavior. |
actions/... | Multiple new action directories have been introduced with Dockerfiles, composite workflows, and action metadata to support the migration. |
.github/workflows | CI configuration files updated to incorporate the new actions and matrix-based testing. |
# use datetime.datetime and convert created at to yyyy.m.d-hhmmss | ||
# GitHub can provide timestamps in different formats, ensure we handle them all using `fromisoformat` | ||
# timestamp: "2023-01-25T10:43:35Z" | ||
# timestamp "2024-07-14T13:17:25-04:00" |
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.
Consider handling ISO timestamps that end with a 'Z' explicitly (for example, by replacing 'Z' with '+00:00') before calling fromisoformat, as some Python versions may raise a ValueError with a trailing 'Z'.
# timestamp "2024-07-14T13:17:25-04:00" | |
# timestamp "2024-07-14T13:17:25-04:00" | |
if iso_timestamp.endswith("Z"): | |
iso_timestamp = iso_timestamp.replace("Z", "+00:00") |
Copilot uses AI. Check for mistakes.
Description
TODO:
Screenshot
Issues Fixed or Closed
Type of Change
.github/...
)Checklist