feat: remove closed issues during syncs
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- backend
Research direction
A linked open pull request (#48) is already working on this issue, so check its status before taking it on. The issue names no files or tests; after confirming the work is available, locate where new issues are fetched and where the user's feed is updated. Done means closed issues are removed during syncs.
Written by the indexing model from the issue text.
Description
What problem would this solve?
Currently closed issues remain on user's feed whereas thay should be filtered out durinc syncs.
What would you like to happen?
Everytime new issues are fetched, check the current issues for closed ones and delete them.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- Avg merge
- 3m
- Merged PRs (30d)
- 22
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
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 tem-ctrl/open-source-guru
-
bug: fix home page overflow on mobile viewPossibly taken @techsamurai430 claimed this 1 day ago. Openbug good first issue help wanted
Difficulty 1/5 Under an hour Newbie friendliness 85/100
tem-ctrl/open-source-guru#28 ·
Maintainers usually reply within 1 day
-
bug: open issues in a new tabPossibly taken @Aryan9891 claimed this 1 day ago. Openbug good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
tem-ctrl/open-source-guru#26 ·
Maintainers usually reply within 1 day
-
feat: automate deploymentPossibly taken @tem-ctrl claimed this 1 day ago. Openenhancement Internal
tem-ctrl/open-source-guru#42 · 1 assignee ·
Maintainers usually reply within 1 day
-
bug: open github repo in a new tabPossibly taken @Aryan9891 claimed this 1 day ago. Openbug good first issue help wanted
Difficulty 1/5 Under an hour Newbie friendliness 25/100
tem-ctrl/open-source-guru#37 ·
Maintainers usually reply within 1 day
-
bug: replace `<domain>` by actual domain in demo api callPossibly taken @dannyward630 claimed this 1 day ago. Openbug good first issue
tem-ctrl/open-source-guru#31 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
All issues in tem-ctrl/open-source-guru
Similar issues
-
freshness freshness:observed-only
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
thoroc/context-radar#280 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
-
documentation story
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
bug category:billing priority:p3 track:fast
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
LanternOps/breeze#9223 ·
Maintainers usually reply within 1 day