apache / apache/hugegraph-computer

Automation analysis

Aperta
#320 0 commenti 1 reazione 0 assegnatari Vedi su GitHub
Lingua principale
Java
Stelle
65
Fork
52
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Descrizione

I'm with the Software Engineering Research Group at the TU Delft, and I am investigating automations. I have looked at your repository and which GitHub workflows and Maven plugins you are using. I hope to provide you with some interesting insights about your repository! I'll give you a quick summary of what I found, and the automation tasks I recommend you to focus on next (:

![Image](https://simchavos.com/assets/thesis/output/apache/incubator-hugegraph-computer_chart.png)

| Level of maturity | Basic | Intermediate | Advanced |
|--------------------|-------|-------------|----------|
| Collaboration | ‎
✅ ***Completed this level!***

| | |
| | ✔️ [Prepare or create documentation artifacts](https://github.com/simchavos/automations/wiki/Automation-Thesis-Wiki#Prepare-or-create-documentation-artifacts)
| ✔️ [Generate documentation from source code](https://github.com/simchavos/automations/wiki/Automation-Thesis-Wiki#Generate-documentation-from-source-code)
❌ [Bot commits](https://github.com/simchavos/automations/wiki/Automation-Thesis-Wiki#Bot-commits)
| ✔️ [Publish documentation](https://github.com/simchavos/automations/wiki/Automation-Thesis-Wiki#Publish-documentation)
✔️ [Issues or PRs management](https://github.com/simchavos/automations/wiki/Automation-Thesis-Wiki#Issues-or-PRs-management)
❌ [Commit validation](https://github.com/simchavos/automations/wiki/Automation-Thesis-Wiki#Commit-validation)
|
| Code quality | ‎
✅ ***Completed this level!***

| | |
| | ✔️ [Run tests](https://github.com/simchavos/automations/wiki/Automation-Thesis-Wiki#Run-tests)
✔️ [Static code style analysis](https://github.com/simchavos/automations/wiki/Automation-Thesis-Wiki#Static-code-style-analysis)
| ✔️ [Generate test reports](https://github.com/simchavos/automations/wiki/Automation-Thesis-Wiki#Generate-test-reports)
❌ [Test coverage and validity](https://github.com/simchavos/automations/wiki/Automation-Thesis-Wiki#Test-coverage-and-validity)
❌ [Automatic code formatting](https://github.com/simchavos/automations/wiki/Automation-Thesis-Wiki#Automatic-code-formatting)
❌ [Static code quality analysis](https://github.com/simchavos/automations/wiki/Automation-Thesis-Wiki#Static-code-quality-analysis)
| ✔️ [Verify packaging correctness](https://github.com/simchavos/automations/wiki/Automation-Thesis-Wiki#Verify-packaging-correctness)
✔️ [Vulnerability scans](https://github.com/simchavos/automations/wiki/Automation-Thesis-Wiki#Vulnerability-scans)
✔️ [Sign artifacts](https://github.com/simchavos/automations/wiki/Automation-Thesis-Wiki#Sign-artifacts)
✔️ [License checks](https://github.com/simchavos/automations/wiki/Automation-Thesis-Wiki#License-checks)
|
| Development | | | ‎
✅ ***Completed this level!***

|
| | ✔️ [Build files configuration](https://github.com/simchavos/automations/wiki/Automation-Thesis-Wiki#Build-files-configuration)
| ✔️ [Build environment configuration](https://github.com/simchavos/automations/wiki/Automation-Thesis-Wiki#Build-environment-configuration)
| ✔️ [Optimization](https://github.com/simchavos/automations/wiki/Automation-Thesis-Wiki#Optimization)
|
| Artifacts | | ‎
✅ ***Completed this level!***

| |
| | ✔️ [Code compilation](https://github.com/simchavos/automations/wiki/Automation-Thesis-Wiki#Code-compilation)
✔️ [Dependency management of artifact](https://github.com/simchavos/automations/wiki/Automation-Thesis-Wiki#Dependency-management-of-artifact)
| ✔️ [Build tasks, resources and configuration](https://github.com/simchavos/automations/wiki/Automation-Thesis-Wiki#Build-tasks,-resources-and-configuration)
✔️ [Packaging](https://github.com/simchavos/automations/wiki/Automation-Thesis-Wiki#Packaging)
✔️ [Release tagging](https://github.com/simchavos/automations/wiki/Automation-Thesis-Wiki#Release-tagging)
✔️ [Publish artifacts to a registry](https://github.com/simchavos/automations/wiki/Automation-Thesis-Wiki#Publish-artifacts-to-a-registry)
| ✔️ [Generate source and metadata artifacts](https://github.com/simchavos/automations/wiki/Automation-Thesis-Wiki#Generate-source-and-metadata-artifacts)
✔️ [Source control management](https://github.com/simchavos/automations/wiki/Automation-Thesis-Wiki#Source-control-management)
❌ [Generate release notes](https://github.com/simchavos/automations/wiki/Automation-Thesis-Wiki#Generate-release-notes)
❌ [Containerization](https://github.com/simchavos/automations/wiki/Automation-Thesis-Wiki#Containerization)
|

# And now? Next steps!
It is not always clear which automation tasks should be prioritized. It is however important to balance your automation efforts, as a uniform level of maturity is most productive. I'm here to help! Below is a list of tasks that you can work on to help level up your maturity across the automation domains:

- Implement **[Automatic code formatting](https://github.com/simchavos/automations/wiki/Automation-Thesis-Wiki#Automatic-code-formatting);** implemented by 10% of GitHub repositories
- Implement **[Test coverage and validity](https://github.com/simchavos/automations/wiki/Automation-Thesis-Wiki#Test-coverage-and-validity);** implemented by 9% of GitHub repositories
# What do you think?
Do you think my analysis is correct, do these recommendations help you? Or have I missed something?

For my master's thesis I'm doing research into the use of automations in GitHub repositories. With my findings, I want to see if I can help out developers with what automations they could focus on. Do you want to help me out? **Leaving a response is much appreciated!**

If you have any other Java/Maven projects you'd like analyzed, you can send me the repositories and I can analyze them for you!

Guida per i contributori

Nessuna guida per i contributori indicizzata per questo repository

Direzione di ricerca

Non sono identificati file del repository, test o punti di ingresso. Esamina l’analisi automation-thesis collegata insieme ai GitHub workflows e ai Maven plugins del repository, quindi determina se viene effettivamente richiesta una modifica concreta all’automazione; l’issue non definisce né un’implementazione né una condizione di completamento.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Valutazione

Stack tecnologico
java
Ambito
build-system, ci-cd, devops
Tipo di issue
Documentazione
Difficoltà
5/5
Tempo stimato
Più di una settimana
Stato di attività
Ferma
Chiarezza
Da chiarire
Idoneità per principianti
15/100

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.