nycolasdiaas/zarea-de-risco

divide .env files and create readme for each session

Open

#67 opened on Jan 18, 2025

View on GitHub
 (0 comments) (0 reactions) (3 assignees)Jupyter Notebook (0 forks)auto 404
documentationenhancementhelp wantedupdate

Repository metrics

Stars
 (1 star)
PR merge metrics
 (PR metrics pending)

Description

It is a good practice to leave each "session" of the project with its own dotev, and with its own updated readme to facilitate execution by another colleague who does not work on the stack.

Contributor guide

Research direction
Identify each session's environment variables and create separate .env files; then document the setup and usage in README files for each session.
Tech stack
python
Domain
documentationdeveloper experience
Issue type
Chore
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
85