Skip to content
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

Test CI workflows #3

Closed
wants to merge 18 commits into from
Closed

Test CI workflows #3

wants to merge 18 commits into from

Conversation

mahendrapaipuri
Copy link
Owner

No description provided.

* Move jupytext module inside src in root

* Create a new module jupytext_config with same behaviour as console script
* Not relevant with Nb 7
* Folder jupyterlab in root will contain all jupyter related stuff

* More TS packages must be added in jupyterlab/packages folder

* Added empty style files

* Removed duplicate LICENSE file
* Use top level package.json to build all extensions at once

* Add lint config to lint TS src

* Add yarn config file that is needed for Yarn 3

* Bump  jupyterlab-jupytext extension node deps to JLab 4

* Modify jupyterlab-jupytext extension's package.json for new repo structure
* Jupyter server and lab extension points are moved to jupyterlab module

* Names are modified appropriately in config files
* Use pyproject.toml inline with PEP621

* Remove unused pylint cfg and add ruff tool

* Remove individual cfg files as everything is consolidated in pyproject.toml
* Lint contents of jupyterlab

* Add yarn.lock for reproducible builds
* Split workflows into logical steps and use nested workflow approach

* General maintainence on workflows to work with new build organization and build system

* Install kernel when quatro is installed. Seems like CI fails otherwise
https://github.com/mahendrapaipuri/jupytext/actions/runs/6561210848/job/17820549979

* Add alls-green action to show CI results in more UI friendly way

* Use optional uploading of build artifacts
@mahendrapaipuri mahendrapaipuri deleted the modernize_build_infra branch November 27, 2023 21:40
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.

1 participant