How to navigate this repository
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 25/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- documentation
Research direction
Start by reviewing the branch links and naming rules documented in the issue, including defaults, TypeScript, versioned, beta, and all-branch views. No repository file or test is named, so first locate the documentation entry point that should contain this guidance. Done means providing a clear, maintained way to navigate the repository and find the relevant branches.
Written by the indexing model from the issue text.
Description
Release
The "defaults" are most similar to what gets publish to the ember-new-output and ember-addon-output repos[^ember-command-output].
[^ember-command-output]: The ember-new-output and ember-addon-output repos have a different tag/branching scheme -- each only has 3 branches -- the default branch is "canary" / "main", and then there is "stable" (meaning "current release"), and then "LTS", which is the last active LTS -- then for each stable release and beta, there are tags. The biggest difference between the new/addon-output repos is that they are only generated with the default CLI arguments (none), and the editor-output repo (this one) may have additional files to help guide online editors.
-
defaults:
-
typescript:
For a specific version
add -v${ember-cli version} to the end
-
defaults:
-
typescript:
Betas
Same as above (for a version), but using the full beta name
-
defaults:
-
typescript:
Everything
all branches can be searched through here:
- Dominant language
- No language data
- Stars
- 1
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
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.
Similar issues
-
sync-en
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
agilepathway/label-checker#640 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
BasedHardware/omi#15662 · 1 comment ·
-
documentation help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100