Skip to content

Conversation

mfisher87
Copy link
Member

@mfisher87 mfisher87 commented Jul 2, 2025

Description

When these steps fail, it's difficult to tell from the logs which step it was that failed. You need some familiarity with the tools.

Add log messages to provide the reader more context.

Checklist

  • PR has a descriptive title and content.
  • PR description contains references to any issues the PR resolves, e.g. Resolves #XXX.
  • PR has one of the labels: documentation, bug, enhancement, feature, maintenance
  • Checks are passing.
    Failing lint checks can be resolved with:
    • pre-commit run --all-files
    • jlpm run lint

📚 Documentation preview: https://jupytergis--798.org.readthedocs.build/en/798/
💡 JupyterLite preview: https://jupytergis--798.org.readthedocs.build/en/798/lite

When these steps fail, it's difficult to tell from the logs which step
it was that failed.
Copy link
Contributor

github-actions bot commented Jul 2, 2025

Binder 👈 Launch a Binder on branch mfisher87/jupytergis/log-schema-gen-steps

Copy link
Contributor

github-actions bot commented Jul 2, 2025

Integration tests report: appsharing.space

@martinRenou martinRenou merged commit 2e8823b into geojupyter:main Jul 3, 2025
15 of 17 checks passed
@mfisher87 mfisher87 deleted the log-schema-gen-steps branch July 3, 2025 14:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants