I14.3 · Watch Linear

Abierto
#95 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
55/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
go

Línea de trabajo

Read the parent issue #17, the provider template, and CONTRIBUTING.md to learn the plugin format and catalog requirements. Verify Linear's official sources and versioning scheme, recording each source URL and check date; leave unknown details as TBD. Add the source catalog entries, saved-source golden tests, a historical breaking-change replay fixture, providers/linear.md, and the docs/plugins.md row; done means daily ingest emits events with source_url and exact source_excerpt and the provider page lists every source.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

good first issue story

Part of https://github.com/patch-it-dev/patch-it-plugins/issues/17

Story

As a developer whose code calls Linear, I want patch-it to know when Linear breaks, deprecates or retires something, so I get the fix before production does.

Subtasks

  • Find Linear's sources and record them with the date checked (verify, don't guess; leave TBD if unknown):
    • deprecations / sunset page
    • API changelog (RSS / Atom if there is one)
    • OpenAPI spec, if published
    • official SDKs and their release notes / changelogs (Python and JS first)
    • API versioning scheme (date-based, path, header, none)
  • Pick the format plugin for each source (OpenAPI, RSS, GitHub Releases, changelog file, registry, prose) and add catalog lines
  • Golden test: a saved copy of each source in, the expected events out
  • One real historical breaking change as a replay fixture
  • Provider page providers/linear.md from the template
  • Add or update its row in docs/plugins.md (see CONTRIBUTING.md)
  • Note what the client needs to fix it (existing handler, or a new fix kind in the client)

Acceptance criteria

  • Daily ingest emits Linear events, each with source_url and an exact source_excerpt
  • The replayed historical change produces the right events
  • The provider page lists every source with its date checked
Lenguaje dominante
Go
Estrellas
0
Forks
0
Merge medio
2 h 59 min
PR fusionados (30 d)
17

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de patch-it-dev/patch-it-plugins

Todos los issues de patch-it-dev/patch-it-plugins

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.