documentcloud / documentcloud/underscore-contrib
Base gh-pages off of master?
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 622
- Forks
- 114
- PR merge metrics
- No merged PRs in 30d
Description
@fogus Any problems with me replacing the current gh-pages branch with one based off of master?
Right now, updating the public docs is a pain because gh-pages doesn't share history with master. I could keep the old history around as an old-gh-pages branch if you'd like.
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
Start by comparing the histories of the gh-pages and master branches, and review how the public docs are published. Confirm whether gh-pages can be based on master and whether the existing history should be retained in an old-gh-pages branch; the work is done when the maintainer-approved branch arrangement is in place.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github
- Domain
- documentation
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100