Skip to content

Conversation

@thomass-dev
Copy link
Collaborator

@github-actions
Copy link
Contributor

Coverage

Coverage Report for skore-hub-project/
FileStmtsMissCoverMissing
skore-hub-project/src/skore_hub_project
   __init__.py19194%35
   protocol.py260100% 
skore-hub-project/src/skore_hub_project/artifact
   __init__.py20100% 
   artifact.py360100% 
   serializer.py280100% 
   upload.py36488%169, 171–172, 174
skore-hub-project/src/skore_hub_project/authentication
   __init__.py00100% 
   login.py19194%26
   logout.py50100% 
   token.py180100% 
skore-hub-project/src/skore_hub_project/client
   __init__.py00100% 
   api.py470100% 
   client.py600100% 
skore-hub-project/src/skore_hub_project/media
   __init__.py60100% 
   data.py42295%26, 28
   feature_importance.py460100% 
   media.py180100% 
   model.py150100% 
   performance.py550100% 
skore-hub-project/src/skore_hub_project/metric
   __init__.py100100% 
   accuracy.py320100% 
   brier_score.py320100% 
   log_loss.py340100% 
   metric.py49197%23
   precision.py600100% 
   r2.py320100% 
   recall.py600100% 
   rmse.py340100% 
   roc_auc.py340100% 
   timing.py87495%51–52, 113–114
skore-hub-project/src/skore_hub_project/project
   __init__.py00100% 
   project.py82297%247, 275
skore-hub-project/src/skore_hub_project/report
   __init__.py30100% 
   cross_validation_report.py72297%210, 251
   estimator_report.py200100% 
   report.py480100% 
TOTAL11671798% 

Tests Skipped Failures Errors Time
134 0 💤 0 ❌ 0 🔥 1m 8s ⏱️

Copy link
Member

@tuscland tuscland left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you @thomass-dev.
Does it need coordination with @retromechs for proper merging, or is it done at release time of skore-hub-project?

@thomass-dev
Copy link
Collaborator Author

Does it need coordination with @retromechs for proper merging, or is it done at release time of skore-hub-project?

We should coordinate with the hub, otherwise the main branch will not work, even if the changes will be effective only at the release of skore-hub-project.

@thomass-dev
Copy link
Collaborator Author

thomass-dev commented Sep 10, 2025

IMO, if we coordinate the release, we can simply rename all the hub APIs without worrying about maintaining the older "artefact" endpoints @retromechs.

@thomass-dev
Copy link
Collaborator Author

Superseded by #2063.

@thomass-dev thomass-dev closed this Oct 7, 2025
@thomass-dev thomass-dev deleted the skore-hub-project-rename-artefact-to-artifact branch October 7, 2025 09:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants