Moving to git-scm.com
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 373
- Forks
- 325
- Avg merge
- 4d 18h
- Merged PRs (30d)
- 1
Description
In https://lore.kernel.org/git/CAP2yMa+PtRADLB2ZL4U3S8X+87Ddz4UZQNMmtEvV5p9nyoq5SA@mail.gmail.com/ @schacon said:
I would love to pull in Git Rev News as a blog on git-scm.com, and/or
link to Taylor's regular posts about what's new in the new versions.
It's such great content and would be nice to have more visible.
Honestly, this whole website would be nice to incorporate:
https://git.github.io/rev_news/
I am going to reply to his message on the list, but maybe we could also discuss it here. And if we agree on moving to git-scm.com, we could perhaps discuss here how it could happen.
cc @jnareb @mjaix @sivaraam @gitster @stepnem
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 by reviewing the Git Rev News site at https://git.github.io/rev_news/ and the referenced git-scm.com discussion. Determine the agreed scope and migration approach from the issue and linked conversation; this issue is done only when the project’s maintainers agree on how, or whether, the site should move.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- content
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100