bannieres NuGet: 3 carnets restants sur main (residu de #26932)

Open
#27,770 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
Half a day
Newbie friendliness
68/100
Issue type
Refactor
Clarity
Clearly specified
Activity status
Active
Tech stack
csharp, jupyter-notebook, python
Domain
content

Research direction

Start by running python scripts/notebook_tools/strip_machine_paths.py --scan-all to confirm the three notebooks listed. Open each notebook under MyIA.AI.Notebooks/GameTheory/SocialChoice/ and MyIA.AI.Notebooks/Search/Part4-Metaheuristics/ and re-execute the cells that produce the NuGet banner, following the C.2 re-execution rule rather than editing output by hand. Done means the same scan returns 0 notebook(s).

Written by the indexing model from the issue text.

Description

Fille de #26932, ouverte au residu (mandat ai-01 c0015-urne-secretaire).

Scope: les 3 carnets qui portent encore une banniere NuGet machine-path sur
main, mesures ce 21/11 par strip_machine_paths.py --scan-all (stock passe de
15 au recensement a 3):

  • MyIA.AI.Notebooks/GameTheory/SocialChoice/ChoixSocial-01-Arrow-Impossibility-Theorem-CSharp.ipynb
  • MyIA.AI.Notebooks/Search/Part4-Metaheuristics/MGS-07d-MichalewiczDixonPrice.ipynb
  • MyIA.AI.Notebooks/Search/Part4-Metaheuristics/MGS-08-LandscapeExplorer.ipynb

paths: MyIA.AI.Notebooks/GameTheory/SocialChoice/ChoixSocial-01-.ipynb, MyIA.AI.Notebooks/Search/Part4-Metaheuristics/MGS-07d-.ipynb, MyIA.AI.Notebooks/Search/Part4-Metaheuristics/MGS-08-*.ipynb

Critere de sortie: python scripts/notebook_tools/strip_machine_paths.py --scan-all rend 0 notebook(s). La garde CI bloquante (#27004) est deja sur
main et empeche toute nouvelle entree -- les fixes se font par re-execution
des cellules (C.2), jamais par edition manuelle de la sortie.

Dominant language
Jupyter Notebook
Stars
18
Forks
162
Avg merge
1d 3h
Merged PRs (30d)
756

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

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 jsboige/CoursIA

All issues in jsboige/CoursIA

Similar issues

More Content issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.