Store actor.id and repo.id for events
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- clickhouse, github
- Domain
- data-engineering, databases
Research direction
Start by locating the stored GitHub event schema and the process that identifies events by event ID. Consult the linked GitHub Event documentation for actor.id and repo.id, then verify that the new columns are populated for incoming events and existing events can be backfilled.
Written by the indexing model from the issue text.
Description
Hi @alexey-milovidov,
Is it possible we store actor.id and repo.id as documented on GitHub Event docs?
So far, we store actor.login and repo.name only, which is convenient to use but fails to handle repo/user rename case.
The process can be we extend those column first and fill with data identified by event id.
- Dominant language
- HTML
- Stars
- 180
- Forks
- 19
- PR merge metrics
- No merged PRs in 30d
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.
More from ClickHouse/github-explorer
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
ClickHouse/github-explorer#8 · 5 comments · 1 reaction ·
-
Difficulty 1/5 Under an hour Newbie friendliness 20/100
ClickHouse/github-explorer#6 · 8 comments ·
-
The `body` attribute of `PullRequestReviewComment` event is from PR itself, not from the comment. Open
Difficulty 3/5 1-2 days Newbie friendliness 25/100
ClickHouse/github-explorer#3 · 1 comment ·
All issues in ClickHouse/github-explorer
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
cisagov/cyhy-reports#149 · 3 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
open-compass/VLMEvalKit#1698 ·