fork: private fork

Open
#20 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
github, javascript
Domain
tooling

Research direction

The issue names no files, tests, or entry points. Start by locating the workflow script that would handle forks and checking the relevant GitHub API documentation for private-fork support. Done means defining and implementing the requested behavior, with verification for the applicable private-repository case.

Written by the indexing model from the issue text.

Description

I suspect the API supports private forks and now that private repos are free this functionality makes more sense.

Dominant language
JavaScript
Stars
16
Forks
3
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from wjmelements/scripts

All issues in wjmelements/scripts

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.