hydrusnetwork / hydrusnetwork/hydrus
Better overview of changes to remote repositories
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3.2k
- Forks
- 207
- PR merge metrics
- No merged PRs in 30d
Description
Currently the ability to manage changes to remote repositories is a bit limited and this is likely to be felt harder going forward if more types of repositories are created.
You can currently search for pending tag additions, but not tag removals. So I would first like to propose the following predicate system:pending remote changes to search all files with pending changes to a remote repository such as the PTR. This also includes files awaiting upload to or, removal from, remote file repositories (like the current system:file service) and other repositories in the future with their own types of content.
Optional is to have settings to list tags, files, and when they're added; notes, ratings, etc. and whether it's a removal or addition.
Going forward it would be highly desirable for a special page with a proper overview of and filters for all pending changes, including petition reasons. Maybe you made a big petition you later realised was faulty and rather than hunting down all possible errors or forgetting all your work and start over you could, in this page, just remove that specific petition group.
Contributor 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.
Research direction
Start by locating the existing pending tag-addition search and the current system:file service handling. Define the scope for the proposed system:pending remote changes predicate and the broader overview page, including filters for additions, removals, petition reasons, tags, files, notes, and ratings; done means pending remote changes can be found and reviewed without manual hunting.
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
- Mostly clear
- Newbie friendliness
- 28/100