processing / processing/processing-contributions
concurrent submissions do not smartly iterate on id numbers
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 8
- Forks
- 8
- Avg merge
- 4d 22h
- Merged PRs (30d)
- 3
Description
When there are two concurrent submissions, they will both be referenced to main, so will have the same id number. That means merges will have to be done one at a time, and after the first, the action for the subsequent submission should be rerun. Perhaps open issues with new-contribution should all rerun upon changes to main?
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 action that handles open issues labeled new-contribution and how submissions reference main and receive id numbers. The work is done when concurrent submissions are handled without conflicting ids, with the intended rerun behavior defined and verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100