popcodeorg / popcodeorg/popcode
Audit export repo's use of the Github API
Open
Nobody has claimed this yet.
performance
- Dominant language
- JavaScript
- Stars
- 191
- Forks
- 143
- Avg merge
- 4d 11h
- Merged PRs (30d)
- 5
Description
- We think we should be able to create all of the files in a single commit, as opposed to a commit per file (and per file changed on repeated export)
- We also think we can publish a .github.io url without needing to create a separate gh-pages branch
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 by locating the export flow and its GitHub API calls, then trace how files and the gh-pages branch are created. Determine whether one commit can contain the full export and whether the published .github.io URL can work without a separate branch; done means both behaviors are verified and the export remains functional.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, javascript
- Domain
- devops, release
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100