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

Omarvio.com

Abierto
  • ¿Algo no está bien?
#3,335 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
42/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
aws
Área
backend, cloud

Línea de trabajo

Start with PUBLISHING.md and the _pattern-model template in aws-samples/serverless-patterns, then clone the model into a new pattern directory with a README and example-pattern.json covering intro.text, resources, and authors. Validate with cd _scripts && npm i and node _scripts/validate.js your-pattern/example-pattern.json. Done means the schema check passes and a PR containing only that one pattern directory is open; note the issue's own "GitHub PR for template" section is empty.

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

Descripción

To submit a template to the Serverless Patterns Collection, submit an issue with the following information.

IMPORTANT
Patterns are intended to be primarily IaC-focused implementations of 2-4 AWS services, with minimum custom code. They should be commonly used combinations that help developers get started quickly. If you have a utility, demo, or application, submit these to the Serverless Repos Collection instead.

ONLY SUBMIT ONE PATTERN CHANGE PER PR. Multiple patterns or files spanning multiple pattern directories will be automatically rejected.

Patterns may take up to 4-6 weeks to review, test, and merge but there is no SLA and can take significantly longer due to other work the team has.

To learn more about submitting a pattern, read the publishing guidelines page.

  1. Use the model template located at https://github.com/aws-samples/serverless-patterns/tree/main/_pattern-model to set up a README, template and any associated code.

  2. THIS PROCESS HAS BEEN SIMPLIFIED. All the information below must be provided in the "example-pattern.json" file cloned from the model **

Note the following information for the model:

  • Description (intro.text) should be a 300-500 word explanation of how the pattern works.
  • Resources should like to AWS documentation and AWS blogs related to the post (1-5 maximum).
  • Author bio may include a LinkedIn and/or Twitter reference and a 1-sentence bio. Use your LinkedIn profile ID and Twitter handle, not URLs.
  • Returning authors with a profile page at https://serverlessland.com/about/your-name can list "contributors": ["content/contributors/your-name.json"] instead of authors.
  • Pull requests check "example-pattern.json" against the pattern schema. To check it locally, run cd _scripts && npm i, then from the repo root node _scripts/validate.js your-pattern/example-pattern.json.

You must ensure that the sections of the model README.md are completed in full.

GitHub PR for template:

Lenguaje dominante
Python
Estrellas
1.8k
Forks
1.1k
Merge medio
1 d 14 h
PR fusionados (30 d)
9

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 aws-samples/serverless-patterns

Todos los issues de aws-samples/serverless-patterns

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.