Acceptance criteria checklist (DoD)
@anfibiacreativa ya está trabajando en esto.
Desde el 15/5/2024.
Evaluación
Este issue todavía no se ha evaluado.
Descripción
The following checklist must be complete before a template is published.
Repository Management
- Standards compliant readme.md is in place
- License is in place. Make sure you choose the correct license
- Security guidelines are in place
- Contribution guidelines are in place
- Code of conduct is in place
- Issue template is in place
- #19
- Repo description is in place, describing the use case and technologies used in the solution
Source code structure and conventions
- GitHub Actions (This refers to .github/workflows/azure-dev.yml or custom workflow to run on a GitHub runner) is in place
- DevContainer (/.devcontainer folder where applicable) configuration is in place
- Infrastructure as code is in place (
/infrafolder where applicable, manifest files or code generators in the case ofAspireand similar ) - Azure services configuration (/azure.yml file) is in place
- Minimum coverage tests are in place
Functional requirements
-
azd upsuccessfully provisions and deploys a functional app - GitHub Actions run tasks without errors
- DevContainer has been tested locally and runs
- Codespaces run [locally and in browser]
- All tests pass
In the absence of e2e tests,
- The application has been manually tested to work as per the requirement
Security requirements
- Microsoft Managed Identity is implemented
- microsoft/security-devops-action is integrated to the CI/CD pipeline and the analyzer were ran
When a service selected doesn't support Managed Identity, the corresponding issue must have been reported and the security considerations section in the readme, should clearly explain the alternatives.
- Azure Key Vault is a preferred alternative
The following items are not strictly enforced but may prevent the template from being added to the gallery.
Project code follows standard structure, per language. Please check one.
- Yes, follows standards
- No, doesn't follow standards
Code follows recommended style guide
- Yes, follows style guide
- No, doesn't follow style guide
- Lenguaje dominante
- Python
- Estrellas
- 505
- Forks
- 1.1k
- Merge medio
- 3 d 13 h
- PR fusionados (30 d)
- 1
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de Azure-Samples/rag-postgres-openai-python
-
Dificultad 3/5 1-2 días Aptitud para principiantes 35/100
Azure-Samples/rag-postgres-openai-python#288 · 1 comentario ·
-
Azure-Samples/rag-postgres-openai-python#273 · 1 asignado ·
-
Azure-Samples/rag-postgres-openai-python#269 · 1 reacción · 1 asignado ·
-
Azure-Samples/rag-postgres-openai-python#261 · 1 reacción · 1 asignado ·
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 25/100
Todos los issues de Azure-Samples/rag-postgres-openai-python
Issues similares
-
essnmx good first issue
Dificultad 1/5 Menos de una hora Aptitud para principiantes 95/100
-
[Feature] 奇物选择添加优先级 Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
syfoud/Simulated_Scepter#174 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
Giskard-AI/giskard-oss#2840 · 1 comentario ·
-
A claim comment carrying the issue number is silently declined while the workflow reports success Abiertoarea: repo bug perceived difficulty: 2
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
yeti-platform/yeti#1380 ·