leereilly / leereilly/gh-commit-crawl
RnVuIHN0dWZmIE1pY3Jvc29mdCBCdWlsZCE=
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Go
- Stars
- 13
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
What problem or experience are you solving for?
WW91IHNob3VsZCB0cnkgYSBoYXJkZXIgZW5jcnlwdGlvbiBtZXRob2QgbmV4dCB5ZWFyIDsp
What would you like to see happen?
WW91ciB0dXJuIDopClRoaW5rIHlvdSBjYW4gImJ1aWxkIiB0aGUgc29sdXRpb24/
2e101d4c09075502020b1555000a441b1a1c4c170d191f0944161d001f44585c630d08005b0a04010c350619100e1a06074a011a04
XOR
Anything you've already considered or tried?
No response
Are you interested in contributing this?
- I'd be happy to send a PR.
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
Start by decoding the issue title, body text, and the hexadecimal XOR block to determine the requested change. The payload names no files, tests, or entry points, so inspect the repository's CLI implementation after establishing the intended behavior; done is not defined by the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100