chaoss / chaoss/CollectOSS

collect_events tries to collect PRs numbers that are assigned to issues

Open
#244 3 comments 0 reactions 0 assignees View on GitHub
challenging first issue
Dominant language
Python
Stars
13
Forks
17
Avg merge
6h 59m
Merged PRs (30d)
1

Description

> [!NOTE]
> Migrated from [augurlabs/augur#3762](https://github.com/augurlabs/augur/issues/3762)
> Originally opened by `@MoralCode` on 2026-03-04

---

on starting to collect this repo, i see:

```
2026-03-04 21:26:08 d0c4fff081f1 collect_events[283] WARNING chaoss/augur - Bulk Github Event task: Could not find related pr. We were searching for: https://api.github.com/repos/chaoss/augur/pulls/3383
2026-03-04 21:26:08 d0c4fff081f1 collect_events[283] WARNING chaoss/augur - Bulk Github Event task: Could not find related pr. We were searching for: https://api.github.com/repos/chaoss/augur/pulls/3376
2026-03-04 21:26:08 d0c4fff081f1 collect_events[283] WARNING chaoss/augur - Bulk Github Event task: Could not find related pr. We were searching for: https://api.github.com/repos/chaoss/augur/pulls/3376
2026-03-04 21:26:08 d0c4fff081f1 collect_events[283] WARNING chaoss/augur - Bulk Github Event task: Could not find related pr. We were searching for: https://api.github.com/repos/chaoss/augur/pulls/3383
2026-03-04 21:26:08 d0c4fff081f1 collect_events[283] WARNING chaoss/augur - Bulk Github Event task: Could not find related pr. We were searching for: https://api.github.com/repos/chaoss/augur/pulls/3382
2026-03-04 21:26:08 d0c4fff081f1 collect_events[283] WARNING chaoss/augur - Bulk Github Event task: Could not find related pr. We were searching for: https://api.github.com/repos/chaoss/augur/pulls/3382
2026-03-04 21:26:08 d0c4fff081f1 collect_events[283] WARNING chaoss/augur - Bulk Github Event task: Could not find related pr. We were searching for: https://api.github.com/repos/chaoss/augur/pulls/3381
```

spot checking one suggests that it is enumerating all PR numbers when in fact github uses the same numerical namespace for issues and PRs, so numbers assigned to issues cant be assigned to a PR, and thus fail.

This is minor but would be maybe a good cleanup issue for a challenging first issue

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.