Explicit configuration of branch information
Open
defer
versions
- Dominant language
- Ruby
- Stars
- 265
- Forks
- 347
- Avg merge
- 3d 15h
- Merged PRs (30d)
- 2
Description
Our JS client docs want to keep a `15.x` branch around even though it is *older* than the current, `7.x` branch of the docs. And they'd like to generate them from a branch called `legacy` in the docs repo. We should modify the docs build so that it can read from some configured branch and it can be explicitly configured with whether or not the branch is "new" or "old".
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.