Add support for handling multiple GitHub orgs
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- github, javascript
- Domain
- devops
Research direction
Start in src/index.js around line 14, where the status-im organization is hardcoded, and trace how the organization is used by the service. The work is done when the comment manager supports multiple GitHub organizations instead of relying on only status-im.
Written by the indexing model from the issue text.
Description
Currently we have hardcoded the status-im org, and it would be better to just support multiple:
https://github.com/status-im/github-comment-manager/blob/4c8fb4c9bcb053a0688f2fe986afe858d92e2bec/src/index.js#L14
- Dominant language
- JavaScript
- Stars
- 3
- Forks
- 0
- 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 status-im/github-comment-manager
-
status-im/github-comment-manager#24 · 3 comments · 1 assignee ·
All issues in status-im/github-comment-manager
Similar issues
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·
-
status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100