cisagov / cisagov/skeleton-aws-lambda-python

Create automated prerelease/release functionality

Aberta
#8 0 comentários 0 reações 0 responsáveis Ver no GitHub
github-actions improvement
Linguagem predominante
Shell
Estrelas
6
Forks
2
Métricas de merge de PRs
Nenhum PR com merge em 30d

Descrição

# 💡 Summary #

Add appropriate GitHub Actions workflow functionality to automatically generate a prerelease/release when a corresponding tag is pushed.

## Motivation and context ##

This would automate what is otherwise the tedious job of downloading Actions artifacts, creating a release manually, and uploading the aforementioned artifacts to that release (again manually). It would allow the appropriate GitHub Actions functionality to kick off when a matching tag is pushed to the repository.

## Implementation notes ##

We can leverage the existing [actions/upload-artifact] and [actions/download-artifact] actions to handle generating and sharing the individual Python version artifacts. We can then use something like [softprops/action-gh-release] in conjunction with the [GitHub automated release notes configuration](https://docs.github.com/en/repositories/releasing-projects-on-github/automatically-generated-release-notes) functionality to create an initial release with artifacts attached. The person creating the tag (and thus the prerelease/release) could then simply check the release and make any necessary edits to the release notes if necessary.

## Acceptance criteria ##

- [ ] When a tag is pushed an appropriate prerelease or release is generated

[actions/upload-artifact]: https://github.com/actions/upload-artifact
[actions/download-artifact]:https://github.com/actions/download-artifact
[softprops/action-gh-release]: https://github.com/softprops/action-gh-release

Guia de contribuição

Abrir o guia de contribuição

Direção de pesquisa

Comece inspecionando os workflows existentes do GitHub Actions no repositório e os nomes dos artefatos produzidos para cada versão do Python. Revise as actions upload-artifact e download-artifact e, em seguida, determine como as tags correspondentes enviadas devem distinguir prereleases de releases e como as notas da release devem ser geradas. Considera-se concluído quando uma tag correspondente enviada cria a release apropriada do GitHub com os artefatos esperados anexados.

Escrita pelo modelo de indexação a partir do texto da issue.

Avaliação

Stack de tecnologia
github-actions, python, shell
Domínio
ci-cd, devops, release
Tipo de issue
Funcionalidade
Dificuldade
4/5
Tempo estimado
3-5 dias
Status de atividade
Estagnada
Clareza
Razoavelmente clara
Facilidade para iniciantes
42/100

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.