automatic-copyright-year: keep README copyright current

Aperta
#189 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@anshulchikhale30-p ci sta già lavorando.

Dal 15/11/2026.

  • #190 di @anshulchikhale30-p — aperta

Valutazione

Difficoltà
3/5
Tempo stimato
Mezza giornata
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
github-actions, python

Direzione di ricerca

Start by reading pull request #190, which is already open against this issue, and the footer line in README.md. Then look at the existing workflows under .github/workflows/ to match conventions, and write a scheduled plus workflow_dispatch job with contents: write that rewrites only the copyright line and checks git diff before committing. Done means a manual run on 2026 produces © 2025-2026 The Stable Order., a second run makes no commit, and the chosen push-vs-PR path is settled against branch protection.

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

Descrizione

documentation enhancement

Summary

The README footer hardcodes the copyright year:

© 2025 The Stable Order.

It should automatically show the current year range. For 2026:

© 2025-2026 The Stable Order.

and on January 1, 2027 it should become:

© 2025-2027 The Stable Order.

without a manual edit.

Proposed behavior

  • Start year stays 2025.
  • End year is the current UTC year.
  • If the current year is 2025, render © 2025 The Stable Order.
  • If the current year is later, render © 2025-<current-year> The Stable Order.
  • The update must be idempotent: if the line already matches, make no commit.

Suggested implementation

Add a small scheduled GitHub Actions workflow, for example:

  • on.schedule with a January 1 cron, plus workflow_dispatch for testing.
  • permissions: contents: write.
  • A short Python or shell step that updates only the copyright line in README.md.
  • Commit only when the value changed.

If main is protected, the workflow can open a PR instead of pushing directly. That can be decided during implementation.

Scope

  • Only the README copyright line.
  • No license text changes.
  • No unrelated README edits.
  • No PR yet; this issue is for discussion and approval first.

Acceptance criteria

  • README shows © 2025-2026 The Stable Order. for 2026.
  • On January 1, 2027 it updates to © 2025-2027 The Stable Order. automatically.
  • Re-running the workflow in the same year makes no change and no empty commit.
  • The workflow can be run manually for testing.
  • Only the copyright line is modified.
  • The chosen approach works with the repository's branch protection rules.

Open question

Should the workflow commit directly to main, or open a PR for review each year?

Lingua principale
Python
Stelle
12
Fork
27
Merge medio
2m
PR unite (30g)
1

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 StabilityNexus/MiniChain

Tutte le issue di StabilityNexus/MiniChain

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.