Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Question about reading public listings on soujava/vagas-java (personal final-year project)

Abierto
#1,956 1 comentario 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
10/100
Tipo de issue
Documentación
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
github
Área
content

Línea de trabajo

The payload identifies the GitHub API endpoint and an external jobs.json output, but no repository file, test, or entry point is named. This is a permission and data-use question rather than an implementation task, so a contributor should wait for maintainer guidance instead of changing code.

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

Descripción

API Java

Hello soujava/vagas-java team,

I'm Manuchehr Qoriev, a computer science student. OmniLadders (https://omniladders.pages.dev) is my own personal final-year project, free and non-commercial, and not run by any university or organization. It helps students around the world find internships and graduate roles.

My script already reads your public job listings, normally once a day, and I would like to check that this is OK with you. For each job the site shows the title, employer, location and a link to the job, and the date where your list gives one, plus a few things derived from the advert (tags, a visa note, a fit score). The same list is also a public file anyone can download. Nothing is sold. This repository has no licence file, so I am asking rather than assuming, and I would be glad to credit it with a link back.

Could you tell me if this is fine, or what you would prefer (a lower rate, an API or feed, only some fields)? If someone else handles this, please forward it.

If you would rather I stop, tell me. I will block it within a few days, so that from the next daily run after that there are no more requests and your listings leave the site, and I will delete the advert text I stored.

Thank you,
Manuchehr Qoriev
OmniLadders · [email protected] · https://omniladders.pages.dev

Technical details, in case someone asks:

  • Requests, once a day (1 in all; a failed request is retried at most twice):
    GET api.github.com/repos/soujava/vagas-java/issues?state=open&per_page=100 (the open issues, one request)
    They send the headers of Chrome on macOS; I can switch to "Mozilla/5.0 (compatible; OmniLadders/1.0; +https://omniladders.pages.dev)" if you prefer.
  • Link check: once a day, a HEAD request to the link of each job shown on the site (your job page or, where a listing provides one, the employer's own application page), following redirects (plus a GET on 403, 404, 405, 410 or a server error), as "Mozilla/5.0 (compatible; OmniLadders/1.0; +https://omniladders.pages.dev)".
  • Stored privately: the advert text, where your site provides it, used to work out labels (visa, degree, experience, language); not published in full. An occasional manual check may send, at most, a job's title, employer, location, link and up to about 2,000 characters of its text to a third-party AI service (Google Gemini or OpenAI).
  • Published: title, employer, location, date, salary if given, a few tags derived from the advert, a visa note, a computed fit score and a link (also as https://omniladders.pages.dev/jobs.json), plus a short quote where an advert states a visa, experience or language requirement.
Lenguaje dominante
TypeScript
Estrellas
1k
Forks
51
Métricas de merge de PR
Sin PR fusionados en 30 d

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

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 soujava/vagas-java

Todos los issues de soujava/vagas-java

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.