Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Move `environment.yml` from `files/` to `data/`

Open
#358 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
38/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Stale
Domain
content

Research direction

Start by inspecting episodes/files/environment.yml and the corresponding episodes/data/ location, then check how the figshare dataset is assembled or updated. Done means the file is in the agreed folder and is not missed from the figshare dataset; the issue does not name a test to run.

Written by the indexing model from the issue text.

Description

How could the content be improved?

The environment.yml files currently resides in the episodes/files/ folder, but it is also part of the dataset on figshare. The file may be missed when updating the figshare dataset. Since environment.yml is not used anywhere in the website, I'm leaning towards moving it to the episodes/data/ folder. Any thoughts?
@tobyhodges We looked at other lesson repositories, and there are some where it's also in episodes/files/. Any strong recommendations to keep it there?

Which part of the content does your suggestion apply to?

environment.yml

Dominant language
HTML
Stars
113
Forks
126
Avg merge
21h 37m
Merged PRs (30d)
2

Getting set up

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 datacarpentry/image-processing

All issues in datacarpentry/image-processing

Similar issues

More Content issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.