UCL / UCL/rsd-engineeringcourse
"Collaboration" page
Open
Nobody has claimed this yet.
2018-19
- Dominant language
- Python
- Stars
- 133
- Forks
- 111
- PR merge metrics
- No merged PRs in 30d
Description
- Commit the resolved file: notebook cell doesn't scroll, message too long
- Distributed VCS in teams with conflicts: in diagram, "pull" should start from shared remote
- The Levels of Git: Should fetch + merge == pull?
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start with the "Collaboration" page and inspect the notebook cell, the distributed VCS diagram, and the "Levels of Git" section mentioned in the issue. Done means the resolved-file message, pull diagram, and fetch/merge versus pull explanation are corrected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, jupyter-notebook
- Domain
- content, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100