"Actually Using Git": create checkpoints along the way
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 45/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- git
- Domain
- documentation
Research direction
Open tutorials/actually-using-git/lessons/conflicting-branches.md and follow the lesson step by step. Add checkpoints after each step showing the expected output of git branch, git status, and cat planets.md. Done means learners can compare their repository state after every step and identify when it diverges.
Written by the indexing model from the issue text.
Description
In tutorials/actually-using-git/lessons/conflicting-branches.md, folks can gloss over small steps and get their repo into an incorrect status. They then go through several steps before they discover this, and don't realize why.
We should provide them with "checkpoints" that show exactly what the output of git branch, git status, and cat planets.md should be after every step.
- Dominant language
- CSS
- Stars
- 6
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from CodeForPhilly/decentralized-data
-
Difficulty 1/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 1/5 Under an hour Newbie friendliness 65/100
-
Difficulty 1/5 Under an hour Newbie friendliness 65/100
-
Difficulty 1/5 Under an hour Newbie friendliness 55/100
-
[Lesson: Install Go] Add links to info about GOPATH and setting environment variablesMay be free again @flyingzumwalt claimed this 3668 days ago, and no pull request is open. Open
CodeForPhilly/decentralized-data#7 · 1 assignee ·
All issues in CodeForPhilly/decentralized-data
Similar issues
-
sync-en
Difficulty 1/5 Under an hour Newbie friendliness 83/100
Maintainers usually reply within 1 day
-
sync-en
Difficulty 1/5 Under an hour Newbie friendliness 86/100
Maintainers usually reply within 3 days
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
profullstack/ugig.net#601 · 1 comment ·
Maintainers usually reply within 1 day
-
discussion welcome security waiting for feedback
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
area:web bug
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
Maintainers usually reply within 1 day