Integrate more high-quality third-party content
Open
Nobody has claimed this yet.
2025 refresh
- Dominant language
- HTML
- Stars
- 2.4k
- Forks
- 1.4k
- Avg merge
- 6d 12h
- Merged PRs (30d)
- 2
Description
There's a ton of awesome content about Git available on the web. One example "Learn Git Branching" comes to mind. Instead of hosting outdated content like https://git-scm.com/docs/giteveryday
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
Review the issue's examples, especially Learn Git Branching and the current giteveryday page. Determine which third-party content should be integrated and what replacing or updating the outdated content would mean. Done should be defined by an agreed content scope and an identified website location for the changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- content, documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100