Make repo public?
Open
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 4
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
@madkinsz and Ryan both suggested it might make sense to do so, I believe. Creating new docs requires a PR approval each time, so I don't see much risk. Pros: other folks could more easily contribute and we could show people our workflow.
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
Review the issue's rationale about repository visibility, contribution access, and PR approval requirements. Confirm the maintainers' decision and repository settings; done means the visibility decision is recorded and the repository is changed only if approved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100