nf-core / nf-core/website

Creation of a new repo shouldn't break the site

Open
#2,329 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
MDX
Stars
98
Forks
298
Avg merge
14h 38m
Merged PRs (30d)
38

Description

Maybe we can pull in from the repo topic somehow and populate the pipeline list that way at the time that the cache is built for modules? Or at build time, but that seems way more error-prone.

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.

Research direction

No files, tests, or entry points are named. Start by tracing the website's module cache and build pipeline to find how creation of a new repository causes the site to break. Done means new repository creation no longer breaks the site and the pipeline list is populated consistently.

Written by the indexing model from the issue text.

Assessment

Domain
build-system, web-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.