Tests to ensure that we can actually upload github gists
Open
Nobody has claimed this yet.
committable
testneeded
- Dominant language
- Raku
- Stars
- 19
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
<AlexDaniel> c: all
<a b c d>».say
<committable6> AlexDaniel, Sorry kid, that's not my department.
<AlexDaniel> c: HEAD
react whenever signal(SIGINT).merge(signal(SIGHUP)) { say ‘hey!’; exit 0 }
<committable6> AlexDaniel, Sorry kid, that's not my department.
Contributor guide
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
The issue names no files or existing tests. Start by locating the GitHub Gist upload path in the repository and its current test coverage; the work is done when tests demonstrate that Gists can be uploaded successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100