feedback should work off of even sources
Open
Nobody has claimed this yet.
mergebot
- Dominant language
- Python
- Stars
- 159
- Forks
- 156
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 16
Description
Technically we can get odd events from any source not just repositories proper, thus we may need to send feedback to any source. As such it would make sense for feedback to work off of sources.
- there's no token associated to sources, so we may need tokens associated with sources (and / or sources associated with projects)
- the repository id we currently send to needs to be remapped to source ids (maybe convert repository_id to a compute which translates to sources)
- or maybe support sources in addition to repos? would be easier to migrate at least
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.
Research direction
Start by tracing the feedback flow and the repository_id, source, project, and token concepts named in the issue. The work is complete when the source-versus-repository model and migration approach are decided, including how feedback reaches non-repository sources.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100