Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

setup: detect a Subversion-hosted project and write the tools/vcs backend config

Chiusa
  • Qualcosa non va?
#1,638 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Una pull request collegata è già stata integrata.

  • #1650 di @potiuk — integrata

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
git, github
Ambito
developer-experience, tooling

Direzione di ricerca

Start with tools/vcs/README.md and the detection steps in plugins/magpie-setup/skills/setup/config.md and adopt.md, then the Source control row in plugins/magpie-setup/templates/project.md. Setup should detect an SVN working copy (svn info or .svn/) and propose the backend without assuming it, and the new project.md key and layout (trunk/branches/tags) must be documented. Done means setup writes the SVN config on an SVN project, and the skills that read upstream_repo or default_branch are listed and degrade cleanly. Confirm the design with maintainers first, since this touches the #1609 backend.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

capability:platform enhancement family:setup family:tools
What should happen

For a project whose source lives in Subversion, setup detects that and writes the VCS backend configuration, so skills using tools/vcs select the Subversion backend (#1609) without the user knowing about --backend or $MAGPIE_VCS.

Why

Setup assumes Git and GitHub throughout. Auto-detection reads the origin remote or runs gh repo view. The project.md template's Source control row defaults to github, with upstream_repo and default_branch as its only settings. For any other VCS the template only says to "declare the sibling tool + its working-copy URL", and it names no key to declare it with. Every svn mention in the setup docs is about the svn-zip method for installing Magpie itself, not the project's own VCS. So an SVN-hosted ASF project gets a Git-shaped configuration, or none.

Which layer

plugins/magpie-setup/skills/setup/config.md and adopt.md, the project.md template (plugins/magpie-setup/templates/project.md, projects/_template/project.md), and tools/vcs/README.md.

Boundary conditions
  • Detect SVN from the working copy (svn info succeeds, or there is a .svn/ directory), then propose the backend. Never assume it.
  • Define the project.md key for the backend (for example vcs_backend: svn) and the working-copy or repository URL, and document both in tools/vcs/README.md.
  • Record the layout the backend supports (trunk / branches/<name> / tags/<name>). Say plainly when a repository uses a different layout.
  • Skills that read upstream_repo or default_branch as GitHub values must degrade cleanly on an SVN project. List them.
Out of scope

The svn-zip install method, and release distribution through svnpubsub (release_dist_backend).

Lingua principale
Python
Stelle
118
Fork
102
Merge medio
13h 35m
PR unite (30g)
362

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di apache/magpie

Tutte le issue di apache/magpie

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.