Readme.md problem
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 159
- Forks
- 156
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 16
Description
Following Readme.md instructions to create first test configuration of runbot we go to the stage "Create a repo for you custom addons repo" and this stage assumes we already should have Runbot project, but it was not created yet. See screenshot below:
It may confuse new users, who is not aknowleged with runbot module terminology.
So, the question is "How to go though this gap?"
At this moment we have only one Project: "R&D".
How should we create "runbot" project before creating repository "runbot"?
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 with the Readme.md instructions at the step titled "Create a repo for you custom addons repo" and compare them with the screenshot and the described R&D project state. Clarify how a user creates or reaches the runbot project before creating the repository, and make the setup path understandable to someone unfamiliar with Runbot terminology.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100