matrix-org / matrix-org/matrix.org
Move the gatsby branch to another repo
Open
Nobody has claimed this yet.
foundation
- Dominant language
- JavaScript
- Stars
- 616
- Forks
- 463
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 19
Description
The gatsby branch unnecessarily clutters the repo and makes it very heavy to clone.
This is not a problem for CF Pages since it's shallow-cloning the repo, but it's a problem for new contributors.
Contributor guide
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
No files or tests are named. Start by inspecting the repository’s branches and clone configuration to determine how the gatsby branch is stored and used; done means the branch is moved to another repository without breaking the website workflow or making normal contributor clones unnecessarily heavy.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- devops
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100