Closed benjaminpkane closed 1 month ago
The recent updates primarily focus on enhancing the GitHub Actions workflows for the repository. A new job named teams
has been added to the pr.yml
workflow, which triggers a workflow in another repository, fiftyone-teams
. Additionally, the all-tests
job now depends on this new teams
job. In the push-release.yml
workflow, the fetch-depth: 0
parameter has been included in the actions/checkout@v4
step to ensure a full repository history is fetched.
File | Change Summary |
---|---|
.github/workflows/pr.yml | Added a new job teams that triggers a workflow in fiftyone-teams and made all-tests depend on it. |
.github/workflows/push-release.yml | Added fetch-depth: 0 parameter to the actions/checkout@v4 step. |
In the land of code, where workflows dance,
A new job namedteams
took a chance.
It reached across to another repo's shore,
Ensuring tests are stronger than before.
Withfetch-depth: 0
, history's complete,
Our CI/CD is now more neat.
Hopping forward, changes in stride,
Together we code, side by side. 🐇✨
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 16.01%. Comparing base (
8b225c4
) to head (445b35f
). Report is 81 commits behind head on develop.:exclamation: Current head 445b35f differs from pull request most recent head b57eea8
Please upload reports for the commit b57eea8 to get more accurate results.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
What changes are proposed in this pull request?
Automated integration into the Teams SDK
What areas of FiftyOne does this PR affect?
fiftyone
Python library changesSummary by CodeRabbit
New Features
Chores
fetch-depth: 0
parameter.