ecosyste-ms / ecosyste-ms/packages

How to handle deleted source repos

Open
#628 3 comments 0 reactions 0 assignees View on GitHub
question
Dominant language
Ruby
Stars
111
Forks
25
Avg merge
3h 47m
Merged PRs (30d)
14

Description

Something interesting has just popped up via a colleague - the package https://pypi.org/project/cron-schedule-triggers/ has deleted the underlying source repo https://gitlab.com/dameon.andersen/cstriggers

What's the best way of this being surfaced via the API? (If it's not already, that is!)

## Upvote & Fund

- We're using [Polar.sh](https://polar.sh/ecosyste-ms) so you can upvote and help fund this issue.
- We receive the funding once the issue is completed & confirmed by you.
- Thank you in advance for helping prioritize & fund our backlog.


Fund with Polar

Contributor guide

Open the contributing guide

Research direction

Start by examining the API response for the PyPI package cron-schedule-triggers and how its GitLab source repository is represented. Compare the available metadata with the deleted repository case described in the issue, then define what API signal or representation should indicate that the source is no longer available.

Written by the indexing model from the issue text.

Assessment

Domain
api, backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.