Skip to content

Try getting rid of double mamba envs by creating a superset env#590

Draft
arjxn-py wants to merge 9 commits intogeojupyter:mainfrom
arjxn-py:duplicate-envs
Draft

Try getting rid of double mamba envs by creating a superset env#590
arjxn-py wants to merge 9 commits intogeojupyter:mainfrom
arjxn-py:duplicate-envs

Conversation

@arjxn-py
Copy link
Member

@arjxn-py arjxn-py commented Apr 1, 2025

Description

Towards #441

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--590.org.readthedocs.build/en/590/
💡 JupyterLite preview: https://jupytergis--590.org.readthedocs.build/en/590/lite

@github-actions
Copy link
Contributor

github-actions bot commented Apr 1, 2025

Binder 👈 Launch a Binder on branch arjxn-py/jupytergis/duplicate-envs

@arjxn-py arjxn-py marked this pull request as draft April 1, 2025 12:43
@arjxn-py arjxn-py added documentation Improvements or additions to documentation maintenance Fixing lint errors, changing project metadata, changing tooling, changing dependencies, etc. labels Apr 1, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Apr 1, 2025

Integration tests report: appsharing.space

@@ -1,12 +1,12 @@
name: jupytergis-docs
name: jupytergis
Copy link
Member

Choose a reason for hiding this comment

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

I would prefer to keep the name as jupytergis-docs because I already have an environment titled jupytergis on my machine and prefer to keep it :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation maintenance Fixing lint errors, changing project metadata, changing tooling, changing dependencies, etc.

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

2 participants