Test against ipywidgets master

Open
#301 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
git, github-actions, jupyter
Domain
ci-cd, testing-qa

Research direction

Start by locating the workflow that tests against development matplotlib and determine whether ipywidgets master belongs there or in a separate workflow. Review the proposed clone and dev-install sequence, then verify the workflow runs weekly and detects breakage in ipympl against the current ipywidgets master.

Written by the indexing model from the issue text.

Description

enhancement

Describe the issue

Now that ipywidgets master is being updated again ipympl should run a weekly workflow checking that nothing breaks. This could either be in the workflow that runs against dev matplotlib or in a separate one.

This might be as simple as:

pushd $(mktemp -d)
git clone https://github.com/jupyter-widgets/ipywidgets.git --single-branch --depth 1
cd ipywidgets
bash dev-install.sh
popd
Dominant language
Jupyter Notebook
Stars
1.7k
Forks
234
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from matplotlib/ipympl

All issues in matplotlib/ipympl

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.